lambdamechanic/tooltest-fix-loop

Tooltest fix loop

You have access to this repository and can run commands.

Goal: make the repository's MCP server(s) conform to the MCP spec as exercised by tooltest.

Figure out how to start the MCP server from this repo (stdio or streamable HTTP).

Select a small, related subset of tools intended to be used together. Default to testing at most 50 tools at a time, and strongly prefer a smaller group. Use --tool-allowlist (or tool_allowlist in MCP input) to enforce this.

Run tooltest against it and fix failures until it exits 0.

If you see "state-machine generator failed to reach minimum sequence length", re-run with --lenient-sourcing or seed values in --state-machine-config.

CLI usage (preferred when you can run commands):

• Use CLI-only flags for debugging, e.g. --trace-all /tmp/tooltest-traces.jsonl.
• Examples: CLI stdio (allowlist example): tooltest stdio --command "<command that starts the repo's MCP server>" --tool-allowlist foo --tool-allowlist bar CLI http (allowlist example): tooltest http --url "http://127.0.0.1:9000/mcp" --tool-allowlist foo --tool-allowlist bar

MCP tool usage (when you must call via MCP):

• Call the tooltest tool with the shared input schema.
• Only fields in the MCP input schema are accepted (CLI-only flags like --json and --trace-all are not supported).
• Example (allowlist):

{
  "target": { "stdio": { "command": "<command that starts the repo's MCP server>" } },
  "tool_allowlist": ["foo", "bar"]
}

Don't rename tools or change schemas unless required; prefer backward-compatible fixes.

Add/adjust tests if needed.

Return a short summary of what you changed and why, plus the final passing tooltest output snippet.