Skip to main content
Glama
Sign In
ratchet-mcp

ratchet-mcp

by deimos-hq
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get signed proof of the decisions on an effect

ratchet_list_receipts
Read-onlyIdempotent

List signed receipts for an effect ID to prove which actions were authorized or refused.

Instructions

Returns a signed receipt for every decision made about one effect, refusals included. Each signature is over the exact bytes in body and verifies offline against the Ed25519 key published at /.well-known/ratchet-receipt-key — you do not have to trust this server to check them. Use this when a human asks you to PROVE an action was or was not authorised, rather than asserting it.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "effect_id": "<effect_id>"
    },
    "name": "ratchet_list_receipts"
  }
}

Input Schema

NameRequiredDescriptionDefault
effect_idYesThe effect to fetch receipts for.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.2.1

TDQS

A4.5/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Beyond the readOnlyHint/idempotentHint/destructiveHint annotations, the description adds substantial behavioral context: receipts are signed, signatures cover exact bytes in `body`, verification works offline against a published Ed25519 key, and the server does not need to be trusted. This meaningfully informs the agent about what the tool guarantees.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is three focused sentences with no wasted words. The core behavior is front-loaded, then the cryptographic detail, then the practical use case. Every sentence earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only single-parameter tool with no output schema, the description sufficiently explains what is returned, what each receipt proves, how verification works, and when the tool should be invoked. Nothing essential is missing for an agent to call it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 100% coverage and already documents `effect_id` as 'The effect to fetch receipts for'. The description mentions fetching receipts for 'one effect', which aligns with the parameter, but does not add additional semantic detail beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb ('Returns'), a specific resource ('signed receipt for every decision made about one effect'), and a notable inclusion ('refusals included'). This clearly distinguishes it from sibling tools like ratchet_list_effects or ratchet_get_effect.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly states when to use the tool: 'Use this when a human asks you to PROVE an action was or was not authorised'. It contrasts with the alternative behavior of merely asserting something, though it does not name a specific sibling tool as an alternative.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools