Skip to main content
Glama

Agent Data Tools: Full list (every tool as its own definition)

Polygon PoS transaction receipt

polygon_receipt
Read-only

Transaction receipt on Polygon PoS (eth_getTransactionReceipt): success or reverted, gas used, effective gas price, fee paid in POL, number of event logs and any contract created. Use to confirm a payment or call went through; for sender, value and calldata use polygon_tx. Input is a 0x-prefixed 64-hex hash; a pending or unknown hash returns 422, uncharged. Example: hash=0x23e86c30c46638b2e9798692fe89327a66aa8569a5d4a566125f655aeb8f80c7. Price $0.01/call via x402 USDC or a card key (/credits), first 25 free; failed calls free. Reads or computes only and changes nothing; each call is charged, so repeats are not 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": {
      "hash": "<hash>"
    },
    "name": "polygon_receipt"
  }
}

Input Schema

NameRequiredDescriptionDefault
hashYes0x-prefixed transaction hash (64 hex characters)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only declare readOnly/openWorld/idempotent-false/non-destructive; the description goes well beyond by disclosing pricing ($0.01/call via x402 or card key, first 25 free, failed calls free, uncharged 422 on pending/unknown hash) and that repeats are charged, which explains the idempotentHint=false. That is exactly the kind of cost and failure behavior an agent cannot infer from annotations.

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?

Front-loaded with purpose, then returns, then usage, then parameter format, example, pricing and safety. Dense and mostly waste-free, though the closing 'reads or computes only and changes nothing' restates readOnlyHint and the repeat-charging note slightly echoes the pricing clause.

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

Completeness5/5

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

No output schema exists, so the description carries the return-value burden itself and does so by enumerating the fields returned and the contract-created case. Combined with error semantics, pricing and the single-parameter format, an agent has everything needed to call it correctly.

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 is already documented as a 0x-prefixed 64-hex hash, so the baseline is 3. The description reinforces the format and provides a concrete example hash, but adds no meaning the schema lacks.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb and resource (transaction receipt on Polygon PoS, aliased to eth_getTransactionReceipt) and enumerates exactly what it returns: status, gas used, effective gas price, fee in POL, log count, contract created. It explicitly distinguishes itself from polygon_tx, which covers sender, value and calldata.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It states the positive use case (confirm a payment or call went through) and names the alternative with the condition that selects it (for sender, value and calldata use polygon_tx). The pending/unknown-hash path is also described, so the agent knows what a failure means rather than guessing.

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.