Skip to main content
Glama

minia2a — hosted x402 API marketplace (HTTP)

x402-gas-price

Gas Price: Gas price across chains. 🆓 5 free trial calls per signed wallet

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": "x402-gas-price"
  }
}

Input Schema

NameRequiredDescriptionDefault
chainNo
networkNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedInput schema / properties / chain / description
      Removed value: -"Chain to process"
    • removedInput schema / properties / network / description
      Removed value: -"Network to process"
  2. First observed

TDQS

C2.4/5.0
Behavior2/5

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

No annotations exist, so the description carries the full burden. It usefully discloses the pricing/auth model (5 free trial calls per signed wallet), but says nothing about what a call returns, whether it queries live chain state, or how unknown/invalid chains are handled.

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?

Very short and front-loaded, but the opener 'Gas Price: Gas price across chains' is redundant restatement of the name, so one of only two sentences is essentially wasted.

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

Completeness2/5

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

For a tool with no annotations, no output schema, and zero parameter documentation, the definition is far too thin. The agent knows neither valid chain/network values nor the response shape, so it cannot invoke this confidently against its many gas siblings.

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?

Both parameters (chain, network) have 0% schema description coverage, and the description does not explain what values they accept, whether they are mutually exclusive or complementary, or what the default is when omitted. The phrase 'across chains' only loosely hints at the chain parameter.

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

Purpose3/5

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

Names a resource (gas price) with cross-chain scope, but the title-restating first clause adds nothing beyond the name and there is no differentiation from the many gas siblings (x402-gas, x402-gas-now, x402-gas-tracker, x402-multi-gas, x402-estimate-gas). An agent cannot tell from this text why it should pick this gas tool over the others.

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

Usage Guidelines2/5

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

No when-to-use guidance, no prerequisites, and no mention of any alternative tool. The only extra sentence concerns trial-call quota, which is a billing note rather than usage routing.

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.