Repository navigation
Add the MCP-01 coverage test - #2517
Merged
Merged
Conversation
Closed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #2516
What
The MCP-01 coverage test of F-MCP (#2423).
McpCoverageTestslists the capabilities MCP-01 names with the tools that cover each one.IToolProviderthe way the host does (AddFluentCmsCore) and fails when:Why
The epic's acceptance asks for a coverage test against the MCP-01 list that passes at the end of M1. Listing unbuilt capabilities with their epics lets it pass today and say exactly what is left. Failing on an unlisted tool keeps the list current as lanes add tools.
Choices worth a look:
JobQueueWorkeronly keeps its polling rhythm. It also needs change set operations on entries and entities, which the change set directory still refuses withitem_kind_unavailable. Its row names F-MCP: MCP server, agent credentials, scopes and caps #2423 until both land.get_published_entrypasses. A name check is coarse, but it stops the obvious mistake. The Core check from Refuse agents' review moves and enforce change set caps #2503 is what actually refuses the move.Tests
The four checks above pass on v2. The full suite ran locally against a
postgres:17container as well as SQLite, and markdownlint passes. No new package and no new project reference.Checklist
v2