Skip to main content
Glama

x402 Data API (Crypto, DeFi, SEC EDGAR, Search, Embeddings, Whisper, OCR)

agent_gas_sponsor_check

[$0.02] Evaluate EIP-4337 Paymaster EntryPoint deposits, live EVM RPC gas fees, and USD UserOperation cost before submitting sponsored or self-funded transactions.

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": "agent_gas_sponsor_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
chainNoTarget chain ('base' or 'ethereum')base
timeout_msNoOptional deadline in ms. If the local LLM would exceed it, the response comes back fast with "degraded": true and non-LLM/cached data
paymaster_addressNoOptional custom EIP-4337 Paymaster address (0x...)
estimated_gas_limitNoEstimated UserOperation gas limit (default 180000)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description does meaningful work: it discloses a $0.02 cost, states the data sources are live RPC reads, and its 'before submitting' framing implies a non-mutating preflight. It still omits what happens on RPC failure, whether results are cached, and what the response contains, and the degraded-timeout behavior lives only in the schema, not the description.

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?

A single dense sentence that front-loads the price tag and the evaluation targets, with no filler. It is slightly overpacked with three resource clauses in one breath, but nothing is wasted.

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

Completeness3/5

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

For a four-parameter, zero-annotation tool with no output schema, the description covers purpose and cost but not returns — an agent cannot tell whether it receives a boolean safe/unsafe verdict, a USD estimate, or raw deposit figures. It is adequate to invoke, but not to predict the outcome.

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 description coverage is 100%, so chain, timeout_ms, paymaster_address, and estimated_gas_limit are already documented in structured form. The description adds no parameter-level meaning beyond the schema (e.g., it doesn't explain when a custom paymaster_address changes the evaluation), so the baseline 3 applies.

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?

Names a specific verb ('Evaluate') and three concrete resources: Paymaster EntryPoint deposits, live EVM RPC gas fees, and USD UserOperation cost. This is far more specific than a tautology. It stops short of 5 because it never distinguishes itself from plausible siblings like agent_preflight or agent_mev_shield_check, which an agent could easily confuse with this pre-submission check.

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

Usage Guidelines3/5

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

The clause 'before submitting sponsored or self-funded transactions' gives a real timing cue, which is more than nothing. However, it offers no exclusions and never names or contrasts an alternative sibling (e.g., when to use this vs. agent_preflight), leaving the choice 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