Skip to main content
Glama

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

Eth call, Polygon contract call

polygon_call
Read-only

Read-only contract call on Polygon PoS (eth_call) at the latest block, without a transaction or gas: send ABI-encoded calldata, or a function signature such as balanceOf(address) with args and the call is encoded and its result decoded for you. Use to read any view function that has no dedicated tool (the example reads USDC totalSupply). Calldata up to 8 KB; a call that reverts is 422 with the reason, uncharged. Example: to=0x3c499c542cEF5E3811e1192ce70d8cC03d5c3359, data=0x18160ddd. 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": {
      "to": "<to>",
      "data": "<data>"
    },
    "name": "polygon_call"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYes0x contract address to call
argsNoArguments for a function signature in data: comma separated, or a JSON array for arrays and tuples
dataYes0x ABI-encoded calldata (4-byte selector plus arguments), or a function signature: totalSupply(), balanceOf(address), or with its result types, balanceOf(address) returns (uint256)
fromNoOptional 0x sender address for calls that check msg.sender
returnsNoResult types to decode when data is a signature without them, for example uint256 or address,uint8

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=false, and destructiveHint=false. The description adds substantial behavior beyond those annotations: latest-block semantics, an 8 KB calldata limit, a 422 response with reason for reverts, failed calls being uncharged, pricing and free-tier details, and repeat calls not being free. This is consistent with the annotations and adds real operational context.

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 description is front-loaded and information-dense, with the purpose in the first sentence and constraints following. It is a single long paragraph with minor repetition between 'Read-only' and 'Reads or computes only and changes nothing,' which slightly reduces scanability.

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

Completeness4/5

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

Covers purpose, usage condition, calldata limit, revert behavior, cost, and that results are decoded. With no output schema, it still does not specify the exact response shape or how multiple return values are formatted, which is a small remaining gap for an agent that needs to parse output.

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 description coverage is 100%, so the baseline is 3. The description adds the 8 KB calldata limit and a concrete to/data example, and it frames the signature-plus-args encoding/decoding path, giving some meaning beyond the schema's per-parameter documentation.

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 and resource: 'Read-only contract call on Polygon PoS (eth_call)' at the latest block, without a transaction or gas. It also distinguishes this from dedicated tools by saying to use it for a view function that has no dedicated tool.

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

Usage Guidelines4/5

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

Gives a clear when-to-use rule: 'Use to read any view function that has no dedicated tool,' plus a concrete totalSupply example. It does not name specific alternatives such as eth_call or polygon_token_balance, but the exclusion is implied by the dedicated-tool condition.

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.