Skip to main content
Glama
Sign In

Agent Data Tools: Chain data

by dev.workers.revmesh2074.agent-data-tools
OverviewDiscussionsAdmin

Polygon PoS gas price

polygon_gas
Read-only

Current gas price on Polygon PoS (eth_gasPrice): gas price, base fee and suggested priority fee in gwei, plus what a plain POL transfer (21,000 gas) costs right now. Takes no input. Use before sending a transaction or to decide whether to wait; for the fee a past transaction actually paid use polygon_receipt. Price $0.002/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.

Input Schema

NameRequiredDescriptionDefault
onlyNoOptional: comma-separated top-level result keys to keep, for a smaller answer (for example only=price,symbol); unknown keys are ignored and an empty match returns the full result

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / only / description
      Previous value: -"Optional: comma-separated top-level result keys to keep, for a smaller answer (for example only=fastestFee,halfHourFee); unknown keys are ignored and an empty match returns the full result"New value: +"Optional: comma-separated top-level result keys to keep, for a smaller answer (for example only=price,symbol); unknown keys are ignored and an empty match returns the full result"
  2. Changed1 schema field changed
    • addedInput schema / properties / only
      Added value: +{
+  "description": "Optional: comma-separated top-level result keys to keep, for a smaller answer (for example only=fastestFee,halfHourFee); unknown keys are ignored and an empty match returns the full result",
+  "type": "string"
+}
  3. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover readOnly/openWorld/non-destructive, but the description adds a real behavioral fact beyond them: per-call pricing ($0.002, first 25 free, failed calls free) and that repeats are charged, which explains the idempotentHint=false. It does not discuss latency, rate limits, or caching, so it is strong but not exhaustive.

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 the core purpose and return contents before pricing and safety details; every clause is informative. The pricing/licensing sentence is dense but does earn its place, though it could be split for readability.

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, yet the description fully specifies the return shape (price, base fee, priority fee in gwei, plus a concrete 21,000-gas transfer cost estimate). Combined with cost and safety disclosure, 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%, so the optional 'only' filter is already fully documented in the schema, establishing the baseline of 3. The description adds nothing about the parameter and its claim that the tool 'takes no input' mildly undercuts the existence of the optional projection parameter.

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 precise verb and resource (current gas price on Polygon PoS), names the underlying RPC method (eth_gasPrice), and enumerates the returned fields (gas price, base fee, priority fee, 21,000-gas transfer cost). It is clearly separable from sibling reads like polygon_gas_history and polygon_receipt.

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 both when-to-use ('before sending a transaction or to decide whether to wait') and when to use an alternative ('for the fee a past transaction actually paid use polygon_receipt'). The only gap is that polygon_gas_history, the other natural alternative, is not mentioned.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Agent Data Tools: Chain data toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources