Under the hoodTier: how much it should matter to you
1Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
MCPArea: what it touches
Internal ChangesKind: in v2.1.275,
Internal ChangesSection of the release
Unclear What the 'mcp-display-only' tool kind represents to a user is not stated in the finding.
What
The registry of per-tool result renderers was restructured so that several plugin-specific tool UI entries are replaced by a single module that's lazily imported. Specifically, the mcp-display-only tool kind now has a getter-backed entry that only imports its display module (displayOnlyMcpToolUi) when that tool type actually needs to be rendered, rather than bundling it eagerly with everything else.
Why
This reduces the amount of code loaded upfront, since MCP display-only tool UI code is now fetched only when a session actually uses that tool type.
How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtWhat the 'mcp-display-only' tool kind represents to a user is not stated in the finding.
