Skip to main content
Glama

X420 agent services

x420_chain_token-metadata

Read-onlyIdempotent

Base token metadata: name, symbol, decimals and totalSupply of an ERC-20 contract on Base mainnet, read from the contract through the public RPC. Source: Base mainnet RPC. Says nothing about legitimacy. Not professional, legal, insurance, engineering, medical, financial or tax advice. Price: $0.02 USDC per call (x402 on Base). This hosted tool does NOT pay and does NOT return the deliverable: it validates the input and returns payment instructions (pay_to, network, price and the x402 URL to pay at). GET the url; read PAYMENT-REQUIRED from the 402; retry with PAYMENT-SIGNATURE (x402 v2). Or run the local x420-mcp server with your own wallet key to pay automatically. Deliverable once paid: JSON: address, name, symbol, decimals, total_supply.

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": {
      "token": "<token>"
    },
    "name": "x420_chain_token-metadata"
  }
}

Input Schema

NameRequiredDescriptionDefault
tokenYes0x ERC-20 contract address

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds substantial behavior beyond them: the $0.02 USDC price, that this endpoint does NOT return the deliverable, the exact x402 handshake (GET url, read PAYMENT-REQUIRED from the 402, retry with PAYMENT-SIGNATURE), and an explicit non-attestation caveat about legitimacy. That is the full cost/response contract an agent needs before calling.

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?

The core capability is front-loaded in sentence one, followed by cost, then the payment protocol, then the deliverable shape — a sensible order. Minor waste remains: 'Source: Base mainnet RPC' restates the RPC detail already given, and the legal disclaimer block is boilerplate rather than selection-relevant.

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

Completeness5/5

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

There is no output schema, so the description must describe returns — it does, listing the exact JSON fields delivered once paid (address, name, symbol, decimals, total_supply). Combined with the payment flow and the non-legitimacy caveat, nothing needed to call it correctly is missing.

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?

Schema coverage is 100% and there is only one parameter, so the schema already carries the baseline. The description adds real constraint beyond it by pinning the address to an ERC-20 contract on Base mainnet, telling the agent an address from another chain is invalid.

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

Purpose5/5

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

The first sentence names a specific verb+resource: reading name, symbol, decimals and totalSupply of an ERC-20 contract, scoped to Base mainnet via public RPC. That distinguishes it from sibling reads such as x420_chain_wallet-balance or x420_chain_proof-of-payment without needing either schema.

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?

It clearly frames the two invocation paths (this hosted tool returns payment instructions; the local x420-mcp server with your own wallet key pays automatically), which is exactly the decision an agent faces. It stops short of stating when-not-to-use or comparing against sibling chain tools, so it is clear context rather than full alternative 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.

Resources