Skip to main content
Glama

Mint the abstention receipt

futility_receipt

Mint the HMAC-signed abstention receipt when the run/source/domain verdict is ABSTAIN.

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": {
      "run_id": "<run_id>",
      "source": "<source>"
    },
    "name": "futility_receipt"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainNo
run_idYes
sourceYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the mutating-but-non-destructive profile is covered structurally. The description adds genuine value by disclosing that the receipt is HMAC-signed. It leaves open important behavior: whether a prior futility_verdict call is required, whether re-minting is idempotent or overwrites, and what happens if the verdict is not ABSTAIN.

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 front-loaded sentence with the action verb first and zero filler. The compressed phrase 'run/source/domain verdict' is slightly opaque and forces the reader to infer the relationship to the three schema fields, which keeps it from a 5.

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?

This is a write operation with three parameters at 0% schema coverage and no output schema. For that complexity, the description should state prerequisites (a verdict must exist and be ABSTAIN), error behavior, and what the minted receipt represents. Only the precondition and signature scheme are covered.

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?

Schema description coverage is 0%, so the description must carry parameter meaning. It names all three parameters ('run/source/domain') and ties them to the verdict precondition, which is more than nothing, but it gives no format, source identifier conventions, or indication that 'domain' is optional while run_id and source are required.

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?

Specific verb plus resource: 'Mint the HMAC-signed abstention receipt'. This clearly separates it from futility_verify_receipt (verification) and futility_waste_report (reporting), though it never names those siblings. The scope, producing a signed artifact rather than a verdict, is unambiguous.

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?

Provides an explicit trigger condition: 'when the run/source/domain verdict is ABSTAIN'. That tells an agent exactly when to call it. It stops short of 5 because it gives no exclusions (e.g. what to do for non-ABSTAIN verdicts) and doesn't route to alternatives such as futility_verify_receipt or futility_verdict by name.

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