{"version":"2.1.280","anchor":"tool-wrapper-object-now-preserves-extra-mcpinfo-fields","canonical_anchor":"tool-wrapper-object-now-preserves-extra-mcpinfo-fields","heading":"Tool wrapper object now preserves extra mcpInfo fields","tier":"internal","area":"MCP","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/tool-wrapper-object-now-preserves-extra-mcpinfo-fields","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### Tool wrapper object now preserves extra mcpInfo fields\n\nTool descriptors built from MCP info no longer drop unlisted fields\n\n**What**\n\nWhen Claude Code builds an internal tool descriptor from an MCP server's tool info (MCP is the Model Context Protocol, used to connect external tools), it now carries over all of the original fields before setting `name`, `underlyingV1ToolName`, and the other explicitly listed properties, instead of dropping any fields that weren't explicitly named.\n\n**Why**\n\nThis prevents information attached to an MCP tool from being silently discarded when Claude Code wraps it internally, which matters if other code later expects those extra fields to be present.\n\n- Area: MCP\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}