Skip to main content
Glama

Consume receipt

ricursor_action_consume

Atomically consumes a receipt immediately before the broker executes. Fails if anything changed.

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": {
      "action_id": "<action_id>",
      "receipt": "<receipt>",
      "baseline_hash": "<baseline_hash>",
      "result_hash": "<result_hash>"
    },
    "name": "ricursor_action_consume"
  }
}

Input Schema

NameRequiredDescriptionDefault
receiptYes
action_idYesUnique per proposed action, 8-80 characters.
result_hashYes
baseline_hashYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

The only annotation is openWorldHint=false, so the description carries most of the behavioral burden. It usefully discloses atomicity and a failure condition on change, which is real added context, but it says nothing about what state is mutated, whether consumption is irreversible, what error is returned, or how the receipt is obtained.

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?

Two short sentences, front-loaded with the core action and followed immediately by the failure behavior. No filler or redundancy; every clause carries information.

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

Completeness3/5

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

For a four-required-parameter mutation tool with no output schema and thin annotations, the description covers purpose and failure mode but leaves the receipt lifecycle, expected errors, and idempotency/retry behavior unexplained. An agent would still need to infer how to acquire a valid receipt before calling.

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 only 25% — only action_id is documented — so the description must compensate. It adds meaning to two of the three undocumented parameters by tying 'receipt' and the hash comparison to the consume precondition ('fails if anything changed'), though it does not clarify baseline_hash vs result_hash or why either may be null.

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

Purpose4/5

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

The description states a specific verb ('consumes') and resource ('a receipt') plus timing ('immediately before the broker executes'), and the atomicity/mutation nature is clear. It does not explicitly distinguish itself from the sibling 'ricursor_action_group_consume' or explain how a receipt differs from a check, so it falls short of a 5.

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

Usage Guidelines3/5

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

The phrase 'immediately before the broker executes' implies the usage context (the final step of the action pipeline), and 'fails if anything changed' hints at a precondition check. However, it never says when to call 'ricursor_action_check' or 'ricursor_action_group_consume' instead, and no explicit exclusion or prerequisite ordering is given.

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