Skip to content

docs(rfd): Add RFD 058 - Typed Content Blocks for Tool Responses#464

Open
JeanMertz wants to merge 1 commit intomainfrom
prr34
Open

docs(rfd): Add RFD 058 - Typed Content Blocks for Tool Responses#464
JeanMertz wants to merge 1 commit intomainfrom
prr34

Conversation

@JeanMertz
Copy link
Collaborator

Introduces RFD 058, which proposes replacing jp_tool::Outcome with typed content blocks for tool responses. Instead of returning opaque strings, tools produce an array of structured text, resource, and question blocks that give JP the metadata it needs to own resource formatting, reason about resource identity, and enable optimizations like deduplication.

The content block schema follows MCP's CallToolResult model, which means MCP tool responses can pass through without lossy conversion. The question block type extends the model to support JP's inquiry system. Raw stdout fallback is preserved as a permanent supported path for tools that don't emit JSON.

Also updates rfd-summaries.json with the new RFD entry and refreshed hashes for RFDs 055–057.

Introduces RFD 058, which proposes replacing `jp_tool::Outcome` with
typed content blocks for tool responses. Instead of returning opaque
strings, tools produce an array of structured `text`, `resource`, and
`question` blocks that give JP the metadata it needs to own resource
formatting, reason about resource identity, and enable optimizations
like deduplication.

The content block schema follows MCP's `CallToolResult` model, which
means MCP tool responses can pass through without lossy conversion. The
`question` block type extends the model to support JP's inquiry system.
Raw stdout fallback is preserved as a permanent supported path for tools
that don't emit JSON.

Also updates `rfd-summaries.json` with the new RFD entry and refreshed
hashes for RFDs 055–057.

Signed-off-by: Jean Mertz <git@jeanmertz.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant