Skip to main content
Glama

Consume group receipt

ricursor_action_group_consume

All-or-nothing consumption before the broker writes the group.

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": {
      "group_id": "<group_id>",
      "receipt": "<receipt>"
    },
    "name": "ricursor_action_group_consume"
  }
}

Input Schema

NameRequiredDescriptionDefault
receiptYes
group_idYesUnique per proposed action, 8-80 characters.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/5.0
Behavior3/5

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

Annotations supply only openWorldHint=false, so the description carries most of the burden. It does add genuine behavioral content: atomicity ('all-or-nothing') and the ordering constraint relative to the broker write. It omits what happens on partial failure, whether a consumed receipt is single-use or retryable, and what a successful call returns.

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?

A single short sentence with no filler, and the key constraint (atomicity, ordering) is front-loaded. Its brevity is efficient rather than padded, though it edges toward under-specification.

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

Completeness2/5

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

For a state-changing, all-or-nothing consumption step with minimal annotations and no output schema, the definition leaves too much unexplained: the meaning of 'receipt', whether the operation is idempotent, and how failure is surfaced. An agent could plausibly call it without knowing the required prior step.

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

Parameters2/5

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

Schema coverage is 50%: group_id is documented in the schema (unique per proposed action, 8-80 chars) and the description does not add to it, while 'receipt' is only typed as string with no explanation of its origin, format, or whether it can be reused. With receipt being the semantically critical parameter, the description fails to compensate for the coverage gap.

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

Purpose3/5

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

The description gives a verb ('consumption') plus a distinguishing property ('all-or-nothing') and a sequencing cue ('before the broker writes the group'), so it is more than a restatement of the name. However, what is being consumed and what a 'group receipt' is in this domain remains opaque, and nothing separates it from siblings such as ricursor_action_group_check or ricursor_action_consume.

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

Usage Guidelines2/5

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

The only usage signal is the implied ordering 'before the broker writes the group', which hints at a commit step but never states when an agent should call this versus the sibling check/consume tools. There are no preconditions, no exclusions, and no stated alternatives.

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