putty
MCPProjectProject

project_finish

Stop the run and report what you built. This is the only way a run ends successfully, and it is refused unless `project_verify` passed during THIS run — a verify from an earlier run does not carry over. The refusal names the verify errors that are still open, so fix the first one and verify again; after three failed attempts on the same error, stop and explain it in the summary instead of looping. Pass a two-to-five line `summary` in the user's terms: what changed and what they can do next. Returns `{ ok, runId, summary }`. Once this succeeds, call nothing further — the run is over.

Stop the run and report what you built. This is the only way a run ends successfully, and it is refused unless project_verify passed during THIS run — a verify from an earlier run does not carry over.

Input

The tool takes a single JSON object. Every field, its type, and an example are on the generated reference at GET /mcp/tools, under this tool's name.

Calling it

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": { "name": "project_finish", "arguments": {} }
}

Put your arguments in place of the empty object. A call that fails comes back as a normal result carrying isError: true and a message naming what went wrong, not as a JSON-RPC protocol error.

Notes

The refusal names the verify errors that are still open, so fix the first one and verify again; after three failed attempts on the same error, stop and explain it in the summary instead of looping. Pass a two-to-five line summary in the user's terms: what changed and what they can do next. Returns { ok, runId, summary }. Once this succeeds, call nothing further — the run is over.

The full request and response shape, and a live playground, live on the generated reference at GET /mcp/tools.

On this page