Skip to main content
Glama
Sign In

Agent Data Tools: Chain data

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

Optimism gas price

op_gas
Read-only

Current gas price on Optimism (eth_gasPrice): gas price, base fee and suggested priority fee in gwei, plus what a plain ETH 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 op_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

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered; the description reinforces this with 'reads or computes only and changes nothing'. It adds genuinely useful non-annotation context on pricing, auth (x402 USDC or card key), free tier, and the fact that repeats are charged, which aligns with idempotentHint=false. It does not, however, describe freshness/staleness of the returned price, which matters for a rate that changes every block.

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 returned values, with usage guidance following. Slight redundancy between 'Price $0.002/call via x402 USDC or a card key' and 'each call is charged, so repeats are not free', which say nearly the same thing twice.

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 fully carries the return-value burden by naming each field and its unit. It also covers cost, auth, and failure behavior, leaving nothing essential an agent needs before calling.

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?

Schema coverage is 100%, so the baseline would be 3, but the description says 'Takes no input' while the schema defines an optional `only` projection parameter. That statement actively under-describes the interface and could lead an agent to skip a useful response-trimming option.

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/resource (current Optimism gas price via eth_gasPrice) and enumerates the returned quantities: gas price, base fee, suggested priority fee in gwei, and the cost of a 21,000-gas ETH transfer. It also names the sibling it is not (op_receipt), so an agent can separate it from surrounding tools without opening the schema.

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 explicit usage conditions ('before sending a transaction or to decide whether to wait') and an exclusion routing to op_receipt for historical/actual paid fees. It stops short of distinguishing itself from op_gas_history and op_estimate_gas, which are the most confusable siblings in this list.

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