Skip to main content
Glama

Quote native gas

agentgas_quote
Read-only

Free price quote: how much USDC (on Base, paid via gasless x402) buys a given amount of native gas (ETH on base/arbitrum/optimism, POL on polygon). Returns price_usdc, breakdown and the exact x402 URL to pay. Rejects bad input or over-capacity before any payment.

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": {
      "chain": "<chain>"
    },
    "name": "agentgas_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoRecipient 0x address (optional for a quote)
usdNoAlternatively, a USD budget for the gas value, e.g. 0.25
chainYesDestination chain for the native gas
payerNoYour paying wallet, to quote your loyalty fee
amountNoNative amount, e.g. 0.000025 (ETH default) or 0.5 (POL). Use amount or usd.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / payer
      Added value: +{
      +  "description": "Your paying wallet, to quote your loyalty fee",
      +  "type": "string"
      +}
  2. Changed1 schema field changed
    • changedInput schema / properties / amount / description
      Previous value: -"Native amount, e.g. 0.0002 (ETH) or 0.5 (POL). Use amount or usd."New value: +"Native amount, e.g. 0.000025 (ETH default) or 0.5 (POL). Use amount or usd."
  3. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, and the description still adds real value: the call is free, no payment occurs, and validation/over-capacity failures happen before any payment attempt. It also discloses the return shape (price_usdc, breakdown, the exact x402 URL). Missing are any notes on rate limits or what the rejection response looks like.

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?

Three tight sentences, front-loaded with the free-quote framing, then accepted chains/units, then return values and failure behavior. Parenthetical qualifiers are dense but each one carries information; nothing is filler.

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 5-parameter read-only quote tool with no output schema, the description covers what it computes, the units per chain, what it returns, and its pre-payment validation behavior. It only lacks an explicit pointer to the purchase/ensure siblings and any error-shape detail.

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, and the description mostly reinforces what the schema already documents. It does add one genuinely new semantic: the native unit varies by chain (ETH on base/arbitrum/optimism, POL on polygon) and payment is USDC on Base, which meaningfully clarifies the 'amount' field beyond the schema.

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?

The description opens with a specific verb+resource ('Free price quote') and precisely scopes the result: how much USDC on Base buys a given amount of native gas on base/arbitrum/optimism/polygon. It is clearly a pricing/quote operation, which implicitly separates it from agentgas_order, but it never names that sibling explicitly to confirm the quote-vs-buy boundary.

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?

Useful context is given: the quote is free, paid via gasless x402, and rejects bad input or over-capacity before any payment, which tells the agent it is safe to call speculatively. It stops short of explicitly directing the agent to follow with agentgas_order (or agentgas_ensure_gas) once the quote is accepted, so the hand-off 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.

Resources