{"version":"2.1.265","anchor":"new-unknown-tools-error-case-for-artifact-mcp-manifests","canonical_anchor":"mcp-connector-manifest-validation-now-catches-unknownmisspe","heading":"MCP manifest validation now flags unknown tool names, with fuzzy-match suggestions and dedicated telemetry","tier":"notice","area":"Artifacts","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265\/e\/new-unknown-tools-error-case-for-artifact-mcp-manifests","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265","markdown":"### MCP manifest validation now flags unknown tool names, with fuzzy-match suggestions and dedicated telemetry\n\nArtifact MCP manifests listing tool names a connector doesn't expose now get a specific unknown_tools error and their own telemetry count\n\n**What**\n\n- Publishing an artifact page whose manifest declares a connector but lists tool names that connector doesn't actually expose now produces a specific `unknown_tools` rejection, explaining that `tools` must be the connector's own top-level tool names (with a hint about MCP-gateway-style connectors).\n\n- The manifest-capability validator cross-checks each connector's declared `tools` against its real top-level tool names, auto-corrects near-matches (case\/underscore variants), and for anything still unmatched emits the new `unknown_tools` malformed-entry kind or a warning listing the connector, the unknown names, and the tools that do exist.\n\n- The `artifact_publish` telemetry event's `malformed_count` is now net of a new `unknown_tools_count` bucket, tracked alongside `opaque_id_count` and `host_unavailable_count`.\n\n**Why** Previously a manifest with a misspelled or nonexistent tool name would likely fail in a less specific or less helpful way. Now the error names the actual problem, suggests likely fixes for near-misses, and is tracked separately in telemetry so this failure mode is easier to diagnose.\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}