Skip to main content
Glama

MNOGO DENEG — pay-per-call crypto & AI APIs (x402)

base-gas

[x402 paid: $0.001 USDC on Base] Live Base gas price in gwei via public RPC (15s cache). tools/call returns the live payment challenge.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

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?

No annotations are provided, so the description carries the burden. It usefully discloses that the tool is x402-paid at $0.001 USDC on Base, uses a public RPC, caches for 15s, and returns a live payment challenge via tools/call; it stops short of describing the auth flow beyond that challenge or rate-limit behavior.

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?

It is a single compact sentence with relevant payment, cache, and source details. The leading bracketed payment tag is slightly less front-loaded than a pure purpose statement, but nothing is redundant.

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 zero-parameter price lookup, it covers source, unit, cache duration, and payment cost/challenge, which is enough to call correctly. It does not spell out the successful response structure or full payment workflow, but no output schema or params exist that would require more.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There are no input parameters, so the baseline is 4 and the description does not need to explain parameter meanings. It correctly adds no parameter detail.

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 states a specific resource and scope: live Base gas price in gwei, fetched via public RPC, with a 15s cache. It does not name a verb or explicitly differentiate from sibling gas tools, so it is clear but not fully routing-grade.

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?

It supplies the paid x402 context and cost, which are prerequisites, but never states when to choose this over tool_gas_base or eth-gas or when not to use it. Usage is only implied by the resource name.

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