{"version":"2.1.239","anchor":"mcp-servers-now-report-how-many-tools-were-dropped-for-bad-s","canonical_anchor":"mcp-servers-now-report-how-many-tools-were-dropped-for-bad-s","heading":"MCP servers now report how many tools were dropped for bad schemas","tier":"notice","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239\/e\/mcp-servers-now-report-how-many-tools-were-dropped-for-bad-s","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239","markdown":"### MCP servers now report how many tools were dropped for bad schemas\n\nMCP servers now tell you how many tools were dropped for malformed schemas.\n\n**What**\n\nWhen an MCP server offers tools whose input schemas are malformed, you now get a line saying how many tools were excluded, instead of those tools quietly not appearing.\n\n**Details**\n\n- A new per-server count message sits alongside the existing message that names the individual server and tool.\n- Produced from the same place that handles the server's dropped-tool notices.\n\n**Evidence**\n\n`tools excluded (invalid input schema)`\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 4\/5\n- Signal: 2\/5"}