test(mcp): add tool selection eval harness - #61
Closed
nilsavenholt wants to merge 2 commits into
Closed
Conversation
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.
Summary
RegisterDeveloperToolsMCP registration pathremote_*design (52 tools), including safety-annotation trade-offsProduction-history basis
The checked-in scenarios are derived from aggregate shapes only. No raw MCP inputs, command arguments/output, workspace identifiers, host names, or credentials are committed. The observed snapshot used for prioritization contained 20,286 persisted MCP requests across six workspaces and 23 tools. In particular, SSH work was frequent and failure-prone enough to justify first-class remote-tool evaluation.
Validation
go test ./scripts/mcp-tool-evalgo test -race ./scripts/mcp-tool-evalgolangci-lint run ./scripts/mcp-tool-eval/...git show --check HEADgo run ./scripts/mcp-tool-eval --listscripts/mcp-tool-evalFull
scripts/githooks/pre-commitwas attempted. Its generated/golden test phase cannot complete in this Developer Workspace because/var/run/docker.sockis absent; existingcliandcoderdDB golden tests fail while trying to start PostgreSQL containers. The hook also formatted one new import group; that change was kept and the targeted checks above were rerun on exact HEAD.A live model A/B is intentionally not fabricated. This workspace currently has no injected
MCP_TOOL_EVAL_MODELorMCP_TOOL_EVAL_API_KEY; the runner is ready to execute against a configured Responses-compatible model endpoint once those are supplied.