Skip to main content
Glama

Principal Reputation for Agents

ingest_receipt

Ingest rail-signed settlement receipt

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "ingest_receipt"
  }
}

Input Schema

NameRequiredDescriptionDefault
receiptNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2/5.0
Behavior1/5

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

With no annotations, the description carries the full burden and discloses nothing: no statement on whether the receipt is verified, whether ingestion is idempotent, what permissions are needed, or what happens on a bad signature. The single sentence restates the title's domain terms without describing behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short, but brevity here comes from under-specification rather than efficiency — the one sentence is jargon with no actionable detail. Nothing is front-loaded beyond the title restatement.

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

Completeness1/5

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

Given an opaque nested-object parameter, no output schema, and no annotations, the definition is far too thin for an agent to invoke this correctly. There is no guidance on payload shape, expected result, or failure modes.

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?

There is one parameter, an untyped nested object at 0% schema description coverage, and the description adds nothing about its structure, required fields, or the signature envelope. 'Rail-signed settlement receipt' only loosely hints at what the object should contain, which is barely beyond the parameter name 'receipt'.

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?

It states a verb+resource (ingest a settlement receipt), which is more than the name alone, but 'rail-signed' and 'ingest' are unexplained domain jargon, so an agent cannot tell whether this verifies, stores, or forwards the receipt. No sibling is named, though the sibling list is clearly unrelated resource families.

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, when-not-to-use, or alternative guidance anywhere in the description. The agent must infer that this is the entry point for submitting signed receipts purely from the tool 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