Skip to main content
Glama

Base Token Safety Inspector

token_safety_check

Base token safety check before you swap or accept a token: ERC-20 metadata, supply, upgradeable proxy, owner / renounced, paused, and risk flags. Read-only, about 1 second. Price: $0.005 USDC on Base via x402.

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": {
      "address": "<address>"
    },
    "name": "token_safety_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does well on the essentials: read-only, ~1 second latency, and a required $0.005 USDC payment on Base via x402 – payment and cost being genuinely valuable pre-call context. It does not cover failure behavior, rate limits, or what a 'risk flag' result looks like, so gaps remain for an unannotated tool.

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?

Front-loaded with the purpose and the checklist of checks, followed by two short sentences covering safety profile, latency, and price. Dense but every clause carries information; only the enumerated check list borders on jargon-stuffing.

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 single-parameter read tool with no output schema and no annotations, the description supplies purpose, scope of returned checks, cost, latency, and side-effect profile. The main shortfall is not specifying address format/chain or the shape of the risk-flag output.

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?

One required parameter at 0% schema coverage, so the schema offers only 'address: string'. The mention of 'ERC-20 metadata' hints that this is a token contract address, but the description never states the expected address format or which chain the address is read on, leaving ambiguity the schema does not resolve.

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?

States a specific verb+resource ('Base token safety check') and enumerates exactly what is inspected: ERC-20 metadata, supply, proxy, owner/renounced, paused, risk flags. The word 'Base' plus the sibling token_deep_safety_check implies a tiered pair, but the description never explicitly contrasts the two, so differentiation is inferred rather than stated.

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?

'before you swap or accept a token' gives a clear trigger condition for calling this tool. It stops short of naming the deep-check sibling as the alternative for higher-stakes cases, so there is no explicit when-not-to-use guidance.

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