Skip to main content
Glama

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

Polygon transaction

polygon_tx
Read-only

Look up a Polygon PoS transaction by hash: sender, recipient, value in POL, nonce, gas limit, the 4-byte function selector and its block. Use to see what was sent or whether it exists; for success or failure and fees paid use polygon_receipt, for emitted events polygon_logs. Input is a 0x-prefixed 64-hex hash; an 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_tx"
  }
}

Input Schema

NameRequiredDescriptionDefault
hashYes0x-prefixed transaction hash (64 hex characters)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare readOnly/openWorld/non-destructive, and the description adds context those annotations cannot carry: unknown hash yields 422 and is uncharged, pricing is $0.01/call via x402 or card key, first 25 free, failed calls free, and repeat calls are not free. That pricing and error-behavior disclosure is exactly the value-add expected on top of 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?

The key facts are front-loaded: purpose first, then alternatives, then input format, then pricing. It is a single dense paragraph where nearly every clause earns its place, though the pricing detail is slightly compressed into a run-on at the end.

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?

With no output schema, the description compensates by listing the returned fields. For a single-parameter read tool it covers purpose, selection, input format, error behavior, and cost, leaving no material gap for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3; the description adds a concrete example hash and restates the 0x-prefixed 64-hex format alongside the 422 behavior for unknown hashes. It adds modest but real value beyond the schema rather than simply repeating it.

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?

States a specific verb ('Look up') and resource ('Polygon PoS transaction by hash') and enumerates the returned fields (sender, recipient, value in POL, nonce, gas limit, selector, block). It explicitly distinguishes itself from polygon_receipt and polygon_logs, so an agent can choose without opening any schema.

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?

Gives an explicit when-to-use ('see what was sent or whether it exists') and names two alternatives with the conditions that select them: polygon_receipt for success/failure and fees, polygon_logs for emitted events. Nothing about tool selection is left to inference.

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.