Skip to main content
Glama

Caelara Labs On-Chain Intelligence

base_erc20_inspector

Inspect an ERC-20 on Base or another EVM chain: name, symbol, decimals, supply, owner, proxy slot and risky function selectors

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

Input Schema

NameRequiredDescriptionDefault
chainNoChain: base|ethereum|arbitrum|optimism (default base)
addressYesToken contract address

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden; it does disclose the concrete data surfaced (including proxy slot and risky function selectors), which signals a read-only inspection rather than a mutation. However it says nothing about behavior on non-contract or unverified addresses, failure modes, rate limits, or whether the inspection is cached — relevant gaps for a no-annotation 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?

A single sentence with the verb, target, and returned fields front-loaded; every clause carries information. It is slightly list-like and could have separated scope from return values, but there is no filler.

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

Completeness3/5

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

With no output schema and no annotations, the description does useful work by enumerating the returned attributes, which is the main thing an agent needs. It still omits error/edge-case behavior and any indication of output shape (field types, nullability for missing owner or proxy slot), leaving real gaps for a tool of this complexity.

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, including the chain enum values and the base default. The description only reiterates that the tool works on Base or another EVM chain, adding no syntax, format, or validation detail beyond the schema. Baseline 3 applies.

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?

Specific verb plus resource: "Inspect an ERC-20 on Base or another EVM chain", followed by an enumeration of the exact attributes returned (name, symbol, decimals, supply, owner, proxy slot, risky selectors). An agent immediately knows this is a read-only token metadata/proxy inspection tool. It does not explicitly distinguish itself from token_safety_composite or solana_mint_auditor, which keeps it from a 5.

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?

Usage is implied by the field list (you call it when you need token metadata, ownership, or proxy/selector risk signals), and the multi-chain scope is stated. But there is no explicit when-to-use / when-not-to-use guidance and no named alternative such as token_safety_composite for a full risk verdict.

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