Skip to main content
Glama

Seal the proof pack

proof_seal
Idempotent

Hashes and closes the proof pack after the work is completed. Needs state WORK_COMPLETED. Never: Issue the invoice. Platform fee CHF 0.05 per accepted call: quote first, then send quote_id, mandate_token and idempotency_key.

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": {
      "mandate_token": "<mandate_token>",
      "flow_id": "<flow_id>",
      "evidence": "<evidence>"
    },
    "name": "proof_seal"
  }
}

Input Schema

NameRequiredDescriptionDefault
flow_idYesThe flow (job) id, which is also its chain id.
evidenceYesWhat proves the work, 1 to 200 items: kind, the SHA-256 of the file (64 hex characters) and a label, e.g. [{"kind": "photo_after", "sha256": "<64 hex>", "label": "new siphon"}].
quote_idNoA valid quote for this capability (quote).
mandate_tokenYesThe mandate token from mandate.create.
idempotency_keyNoRequired on every mutate and money call; a retry with the same key returns the same result and is not charged again.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / evidence / description
      Added value: +"What proves the work, 1 to 200 items: kind, the SHA-256 of the file (64 hex characters) and a label, e.g. [{\"kind\": \"photo_after\", \"sha256\": \"<64 hex>\", \"label\": \"new siphon\"}]."
  2. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations cover safety (readOnly=false, idempotent=true, destructive=false), and the description adds genuinely new behavior: the WORK_COMPLETED state gate, the CHF 0.05 platform fee per accepted call, the quote-then-execute ordering, and that a repeat idempotency_key is not re-charged. That is exactly the money/auth context annotations can't express.

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

Conciseness4/5

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

Three tight sentences, front-loaded with the action and precondition, with no filler. The telegraphic 'Never: Issue the invoice' phrasing is slightly clipped but still parseable.

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

Completeness4/5

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

For a paid mutation with a state gate, the description covers prerequisites, the exclusion, the fee, and idempotency. It doesn't say what sealing returns (e.g., a seal/hash reference), which leaves a small gap given there is no output schema.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3. The description earns a bump by giving the call sequence ('quote first, then send quote_id, mandate_token and idempotency_key'), which tells the agent about ordering and coupling among parameters that the schema alone does not.

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?

States a specific verb and resource ('Hashes and closes the proof pack') with a clear completion precondition. It also distinguishes itself from the neighboring invoice tool with 'Never: Issue the invoice', so an agent can separate it from invoice_issue without opening either schema.

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?

Gives an explicit precondition ('Needs state WORK_COMPLETED') and an explicit exclusion ('Never: Issue the invoice'), plus the quote-first ordering. What's missing is a positive pointer to the sibling to use for the excluded action and any note on when sealing is premature vs. final.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources