Skip to main content
Glama

Get Compliance Receipt

get_compliance_receipt
Read-onlyIdempotent

Retrieve a tamper-evident compliance receipt by UUID. Contains XRPL tx hash, agent wallet, endpoint, amount, and timestamp. Free.

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": {
      "receipt_id": "<receipt_id>"
    },
    "name": "get_compliance_receipt"
  }
}

Input Schema

NameRequiredDescriptionDefault
receipt_idYesCompliance receipt UUID returned at settlement

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / receipt_id / description
      Added value: +"Compliance receipt UUID returned at settlement"
  2. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile needs no restating. The description contributes genuinely new behavioral context: the receipt is tamper-evident, what fields it contains, and that the call is free — cost being a real selection factor among siblings. It omits error behavior for an unknown or expired UUID.

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?

Three short sentences, front-loaded with the verb and identifier, followed by payload contents and a cost note. No filler and nothing an agent must scan past to find the essential information.

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 simple one-parameter read tool with full annotation coverage and no output schema, the description carries what is needed by naming the returned fields and the cost. The only gap is the failure mode when a receipt ID is invalid or not found, which is a minor omission for a read-only lookup.

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 coverage is 100% and the single parameter already documents itself as the UUID returned at settlement, so the schema does the heavy lifting. The description's 'by UUID' reinforces the identifier type but adds nothing the schema doesn't already say, which matches the baseline-3 rule for high-coverage schemas.

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 and resource — 'Retrieve a tamper-evident compliance receipt by UUID' — and enumerates the payload contents, so an agent knows exactly what this returns. It stops short of naming which sibling to prefer (e.g., get_invoice vs get_agent_passport), but the resource itself is distinctive enough to be unambiguous.

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?

There is no when-to-use or when-not-to-use guidance and no alternative is named. The only usage-adjacent information is 'Free' and the schema note that the UUID is 'returned at settlement', which is context but not routing guidance.

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