[GH-ISSUE #23] Replace generic MCP outputs with exact agent-first tool contracts #11

New issue

Closed

opened 2026-10-15 18:19:52 +00:00 by bsakaguchi · 0 comments

bsakaguchi commented

2026-10-15 18:19:52 +00:00

Owner

Originally created by @morluto on GitHub (Jul 12, 2026).
Original GitHub issue: https://github.com/morluto/rea/issues/23

Problem

Most tools use a generic { result: unknown } output schema and one-line descriptions. Agents cannot determine output structure, exhaustiveness, side effects, limitations, or the correct next tool.

Scope

For every public tool define exact schemas, purpose, recommended use, bounded behavior, pagination, side effects, provider limitations, and suggested preceding/following tools.

Acceptance criteria

No public tool uses an unrestricted generic result schema.
Contract snapshots cover descriptions, annotations, examples, and outputs.
Pseudocode is distinguished from original or compilable source.
Structured content requires no prose parsing.

Originally created by @morluto on GitHub (Jul 12, 2026). Original GitHub issue: https://github.com/morluto/rea/issues/23 ## Problem Most tools use a generic `{ result: unknown }` output schema and one-line descriptions. Agents cannot determine output structure, exhaustiveness, side effects, limitations, or the correct next tool. ## Scope For every public tool define exact schemas, purpose, recommended use, bounded behavior, pagination, side effects, provider limitations, and suggested preceding/following tools. ## Acceptance criteria - No public tool uses an unrestricted generic result schema. - Contract snapshots cover descriptions, annotations, examples, and outputs. - Pseudocode is distinguished from original or compilable source. - Structured content requires no prose parsing.

bsakaguchi

2026-10-15 18:19:52 +00:00