Skip to main content
Glama

Matchmaking rating for agent selection

ingest_receipt

Ingest verified receipt (verifier-signed)

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.4/5.0
Behavior2/5

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

With no annotations, the description carries the full burden. It discloses only that the receipt should be verifier-signed; it says nothing about side effects, idempotency, whether ingestion is rejected on invalid signatures, permissions, or what happens to previously ingested receipts. That is a substantial gap for an ingest/mutation-style tool.

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

Conciseness3/5

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

The description is a single front-loaded sentence fragment with no wasted words, but it is terse to the point of under-specification rather than genuinely concise. The structure is clean; the content is too thin.

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?

No annotations, no output schema, and a nested object parameter mean the description must do more work. It only conveys that the receipt is verifier-signed, leaving an agent without enough context to invoke the tool confidently or understand the result.

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 nested-object parameter with 0% schema description coverage. The description's phrase 'verified receipt (verifier-signed)' hints at the expected content but does not describe the object's fields, required signature structure, or format. It does not compensate for the schema 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 ('Ingest') and a resource ('receipt'), and the parenthetical narrows the input to a verifier-signed receipt. However, 'ingest' is vague about what actually happens (store? verify again? record on a ledger?), and nothing distinguishes its role from siblings query_rating and rank_agents, which appear unrelated.

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 guidance on when to call this versus other tools, no prerequisites, and no statement about what to do with an unverified or unsigned receipt. The only implied condition is that the receipt must be verifier-signed, which is embedded in the parenthetical rather than framed as a usage rule.

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