Skip to main content
Glama

Verify a receipt

futility_verify_receipt
Read-only

Verify a receipt payload {receipt, signature}; total rejection with a reason on malformed/forged input.

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": "<receipt>",
      "signature": "<signature>"
    },
    "name": "futility_verify_receipt"
  }
}

Input Schema

NameRequiredDescriptionDefault
receiptYes
signatureYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare this a safe read (readOnlyHint=true, destructiveHint=false), so the description is free to add value elsewhere, and it does by disclosing failure semantics: malformed or forged payloads are rejected outright with a reason. However, it says nothing about what a successful verification returns, despite there being no output schema to fall back on.

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 dense sentence with no filler, front-loading the action and adding the failure behavior immediately after. It is efficient, though the semicolon-joined second clause reads as a fragment rather than a structured statement.

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 nested-object tool with no output schema, and the description does not describe the receipt's structure, the signature's expected format, or the shape of a successful verification result. For a verification tool with zero schema documentation, the definition is too thin to let an agent call it with confidence.

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 description coverage is 0%, so the description must carry parameter meaning, and it largely restates the two field names. The receipt is a nested object whose internal shape is never hinted at, and the signature's encoding or provenance is left unspecified.

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 pairs a specific verb (verify) with a specific resource (a receipt payload), so the operation is unambiguous. It does not, however, distinguish this from the sibling tools (futility_receipt, futility_verdict, futility_judge), leaving the agent to infer the boundary from names alone.

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 routing to alternatives. The clause about forged input describes a runtime outcome, not the conditions under which an agent should pick this tool over futility_receipt or futility_verdict.

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