Skip to main content
Glama

Paid public-data feeds (x402, 0.002 USD)

Base ERC-20 pre-trade check from the chain itself in one call: contract or not, name, symbol, supply, owner and renounce

base_token_check
Read-onlyIdempotent

Base ERC-20 pre-trade check from the chain itself in one call: contract or not, name, symbol, supply, owner and renounced status, upgradeable-proxy slots, mint/blacklist/pause/fee-setter selectors in the bytecode, Uniswap v3 pools vs WETH and USDC with quote-side balances, risk flags and a 0-100 score (token=0x...). Static inspection, no buy/sell simulation. Not financial advice. Pay per call $0.002 USDC on Base via x402.

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_token_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
tokenNoBase ERC-20 address, 0x...
x_paymentNosigned x402 payment (X-PAYMENT header value); omit on the first call to receive the price and payment requirements

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior5/5

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

Annotations only cover read-only/idempotent/non-destructive/open-world, and the description adds behavior those fields cannot express: the cost ($0.002 USDC on Base via x402), the two-step payment handshake when x_payment is omitted, and the fact that analysis is static bytecode/state inspection rather than simulated trading. That is exactly the extra context an agent needs to avoid calling it in a loop or misreading the score as a trade simulation.

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?

It is heavily front-loaded and the output enumeration earns its place given there is no output schema, but the core is a single sprawling comma-chained sentence that largely mirrors the title and is hard to scan. 'Not financial advice' is boilerplate that adds little, and the density slows parsing of the key facts.

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?

With no output schema, the description must enumerate return content and it does so exhaustively, down to quote-side balances and the 0-100 score. Payment requirements, the first-call handshake, and the static-only limitation are all covered, so an agent has enough to invoke correctly on the first attempt.

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 both parameters are already documented in the schema. The description only restates 'token=0x...' and adds no format, constraint, or interpretation detail beyond what the schema carries, which is the baseline 3 case.

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 description names a specific verb and resource ('Base ERC-20 pre-trade check from the chain itself') and enumerates exactly what is inspected: contract existence, name, symbol, supply, owner, renounce status, proxy slots, mint/blacklist/pause/fee-setter selectors, Uniswap v3 pools, risk flags and a 0-100 score. It also states the boundary ('Static inspection, no buy/sell simulation'), so an agent can tell precisely what class of answer this returns versus an unrelated sibling like security_headers or domain_rdap.

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?

The 'pre-trade check' framing gives a clear use context, and 'Static inspection, no buy/sell simulation' rules out a plausible wrong expectation. The payment workflow instruction ('omit on the first call to receive the price and payment requirements') is explicit. It stops short of naming any alternative tool or exclusion conditions, so it lands at 4 rather than 5.

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