tooltest-fix-loop

Estrelas10

Forks2

Atualizado30 de janeiro de 2026 às 02:36

Use when running tooltest to validate MCP servers, interpret failures, and iterate fixes in this repo.

Instalação

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Fonte

lambdamechanic

lambdamechanic/tooltest

Abrir repositório GitHub Ver repositórios do creator

Download

Ocupações relacionadasSOC

Baseado na classificação ocupacional SOC

Analistas de garantia de qualidade de software e testadoresInformática e Matemática·SOC 15-1253

SKILL.md

readonly

name	tooltest-fix-loop
description	Use when running tooltest to validate MCP servers, interpret failures, and iterate fixes in this repo.

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.

Mais deste repositório

mesmo repositório

bd-to-br-migration

lambdamechanic/tooltest

Migrate docs from bd (beads) to br (beads_rust). Use when updating AGENTS.md, converting bd commands, "bd sync" → "br sync --flush-only", or beads migration.

2026-01-2810

lambda-workflow

lambdamechanic/tooltest

One lifecycle for Lambda repos: choose a br issue, start work, land the PR, and watch GitHub via Dumbwaiter MCP until it merges.

2026-01-2710

beads

lambdamechanic/tooltest

Git-backed issue tracker for multi-session work with dependencies and persistent memory across conversation compaction. Use when work spans sessions, has blockers, or needs context recovery after compaction.

2026-01-2710

testing-patterns

lambdamechanic/tooltest

Testing patterns and standards for this codebase, including async effects, fakes vs mocks, and property-based testing.

2026-01-2710

galahad

lambdamechanic/tooltest

how to approach tests, types and coverage

2025-12-3010

rust-guidelines

lambdamechanic/tooltest

Pragmatic Rust conventions to keep code readable, testable, and performant for this project.

2025-12-2110

name	tooltest-fix-loop
description	Use when running tooltest to validate MCP servers, interpret failures, and iterate fixes in this repo.

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).

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.