Skip to main content
Glama

Agent Data Tools: Full list (every tool as its own definition)

Network info, Base and USDC: Base network facts for payment clients: chain id, USDC contract, RPC and explorer URLs

network
Read-only

Reference facts for paying and reading on Base mainnet: chain id, native USDC contract and decimals, block explorer and public RPC URLs, and the x402 network identifier. Use to configure an x402 or Base client. Price $0.01/call via x402 USDC or a card key (/credits), first 25 free; failed calls free. Reads or computes only and changes nothing; each call is charged, so repeats are not free.

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

Input Schema

NameRequiredDescriptionDefault
onlyNoOptional: comma-separated top-level result keys to keep, for a smaller answer (for example only=price,symbol); unknown keys are ignored and an empty match returns the full result

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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=true, destructiveHint=false, openWorldHint=false, but the description adds real information beyond them: the $0.01/call price via x402 USDC or card key, 25 free calls, failed calls free, and that repeats are charged. That last point usefully explains the non-obvious idempotentHint=false. It omits any note on latency, caching, or response envelope, so it is strong rather than complete.

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 front-loaded sentences: what it returns, who it is for, then commercial and safety terms. Little waste, though the pricing detail is stated twice in compressed form ('charged' and 'repeats are not free'), which is mild redundancy rather than bloat.

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?

With no output schema, the description carries the return-value burden and handles it by enumerating the exact fact keys returned, plus cost and side-effect profile. It does not state the response shape (JSON object) or how 'only' interacts with the returned keys, a minor gap for a zero-required-parameter reference tool.

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% and the single optional 'only' parameter is fully documented in the schema, so the baseline is 3. The description never mentions the projection parameter or its effect on result size, adding nothing beyond structured data.

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 names a concrete resource ('Reference facts for paying and reading on Base mainnet') and enumerates exactly what it returns: chain id, native USDC contract and decimals, explorer and RPC URLs, and the x402 network identifier. This clearly separates it from the per-chain token_info and is_contract siblings, though it never names or contrasts an alternative explicitly.

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?

'Use to configure an x402 or Base client' gives a clear, actionable context for invocation. It stops short of exclusions, i.e. it never says when not to use it or what to use instead when a per-chain token lookup is actually needed, so it lands just below the top mark.

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.