Advertise MCP tool safety and structured output metadata #39

Closed
opened 2026-07-30 07:30:12 +00:00 by coilyco-ops · 1 comment
Member

Outcome

Make Ward MCP tool contracts easier for ChatGPT, Codex, and other MCP clients to select, display, and confirm correctly without adding per-tool handwritten code.

Acceptance

  • Local opcore-backed tools advertise a human title and user-goal description.
  • readOnlyHint, destructiveHint, idempotentHint, and openWorldHint reflect the operation's HTTP behavior and policy descriptor.
  • Local tools advertise an output schema and return conforming structuredContent while retaining text content for compatibility.
  • The built-in exact-parameter SSM reader advertises read-only metadata and a specific structured result schema.
  • Allowlisted upstream proxy tools preserve upstream-owned metadata and result contracts.
  • Initialize includes compact server instructions describing the policy boundary.
  • Transport-level tests cover tool listing, classification, output schemas, structured results, and initialization.
  • README, DESIGN, FEATURES, and worked specs document the derived contract.
  • Ward-routed validation and the repository pre-commit suite pass.
## Outcome Make Ward MCP tool contracts easier for ChatGPT, Codex, and other MCP clients to select, display, and confirm correctly without adding per-tool handwritten code. ## Acceptance * Local opcore-backed tools advertise a human title and user-goal description. * `readOnlyHint`, `destructiveHint`, `idempotentHint`, and `openWorldHint` reflect the operation's HTTP behavior and policy descriptor. * Local tools advertise an output schema and return conforming `structuredContent` while retaining text content for compatibility. * The built-in exact-parameter SSM reader advertises read-only metadata and a specific structured result schema. * Allowlisted upstream proxy tools preserve upstream-owned metadata and result contracts. * Initialize includes compact server instructions describing the policy boundary. * Transport-level tests cover tool listing, classification, output schemas, structured results, and initialization. * README, DESIGN, FEATURES, and worked specs document the derived contract. * Ward-routed validation and the repository pre-commit suite pass.
Author
Member

Landed on canonical main in commit 51707ba.

Validation:

  • ward exec fmt
  • ward exec test
  • ward exec vet
  • ward exec build
  • git diff --check

The implementation derives local tool titles and safety annotations, publishes output schemas with matching structured results, adds server instructions, adds specific SSM metadata, preserves upstream proxy contracts, and updates README, DESIGN, FEATURES, and worked specs.

Landed on canonical `main` in commit `51707ba`. Validation: * `ward exec fmt` * `ward exec test` * `ward exec vet` * `ward exec build` * `git diff --check` The implementation derives local tool titles and safety annotations, publishes output schemas with matching structured results, adds server instructions, adds specific SSM metadata, preserves upstream proxy contracts, and updates README, DESIGN, FEATURES, and worked specs.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
coilyco-flight-deck/mcp-beaver#39
No description provided.