Skip to main content
All 22 tools at MCP v1 GA. Each handler lives in apps/mcp/src/tools/<tool>.ts. Format per tool: name · scope · category · annotations. Full input/output schemas in the source file.

Write tools (/write endpoint, 60 req/min cap)

Read tools (/read endpoint, 300 req/min cap)

Treasury tools (/treasury endpoint, 10 req/min cap)

Step-up flow (shared)

Write/treasury tools over the envelope return JSON-RPC -32003 with:
Surface the URL to the user. They biometric-approve on the Glide sheet. Retry the tool with step_up_sigil=<sigil>. CAS-claim guarantees first-use-only; a 5-minute grace window returns the same payload to benign polls (prevents re-asking on network retry).

Annotations honored by MCP clients

Per MCP 2025-11-25 spec:
  • readOnlyHint: no side effects.
  • destructiveHint: cannot be undone by the tool itself.
  • idempotentHint: safe to retry with same params.
  • openWorldHint: interacts with external systems (x402.pay, facilitators).
Glide extension:
  • requiresHumanApproval: client SHOULD surface the step-up flow to the user even before calling.
Official Glide clients (Claude Desktop, ChatGPT Apps, Vertex) verify emitted annotations match the client-side registry; mismatch = refuse to execute. Custom runtimes that bypass this client-side check are still caught by the server-side annotation check on each call.