Skip to main content
Glama

Agent Exchange store

Base gas price (live)

kyreos_base_gas_price
Read-only

[Kyreos, 0.001 USDC per call via x402 on Base] Current Base gas price in wei and gwei from a public RPC. One call, JSON back. Built from what paying wallets already buy: chain reads. Input: {}. HTTP: GET https://store.agentexchange.work/w/base-gas-price?q=... Call once without x_payment to get the x402 payment terms (0.001 USDC); call again with x_payment (the signed x402 payment) to get the result.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "kyreos_base_gas_price"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNo{}
x_paymentNobase64 x402 payment payload for the terms returned on the first call (0.001 USDC on Base)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Beyond the readOnlyHint/openWorldHint annotations, it discloses the cost (0.001 USDC per call via x402 on Base), the payment handshake, the transport (HTTP GET to a named endpoint), and that the response is JSON. It does not mention rate limits, failure behavior when payment is invalid, or caching/staleness of the RPC value.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The payment protocol and cost are front-loaded and useful, but the sentence "Built from what paying wallets already buy: chain reads" is marketing filler that adds nothing actionable, and the endpoint URL ends in a dangling "?q=..." that muddies rather than clarifies.

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?

For a read-only, no-output-schema tool the description covers the essentials: what is returned, in what units, at what price, and the exact two-step invocation. The only real gap is the undocumented q parameter, which an agent must guess at.

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 baseline is 3. The description usefully explains x_payment's role in the two-call sequence, but it never explains the q parameter and its schema text is literally "{}", while the prose says "Input: {}" — creating mild ambiguity about whether q is needed.

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

Purpose4/5

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

States a specific verb and resource: "Current Base gas price in wei and gwei from a public RPC", plus the units returned. It does not distinguish itself from the sibling chain_gas_price or explain why a paid variant exists beyond the pricing note, so it is clear but not sibling-differentiating.

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 concrete procedural rule that most agents would otherwise get wrong: call once without x_payment to receive the 0.001 USDC terms, then call again with the signed payload. It lacks guidance on when to prefer this over a free gas-price sibling, which keeps it below a 5.

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.

Resources