Skip to main content
Glama
@caelaralabs/mcp

@caelaralabs/mcp

caelara_crypto_base_erc20_inspector

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

Instructions

[On-Chain Intelligence] Inspect an ERC-20 on Base or another EVM chain: name, symbol, decimals, supply, owner, proxy slot and risky function selectors Measured p50 12 ms, p95 14 ms (2026-11-21, benchmarks.caelaralabs.com). Calls https://crypto.caelaralabs.com.

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": "caelara_crypto_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 observedv1.0.1

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It adds useful signals (returned fields, p50/p95 latency, endpoint host) but never states that the call is read-only, what auth or rate limits apply, whether any chain requires an API key, or how errors/unsupported tokens are reported. For an unannotated tool, those omissions are material.

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?

The intent is front-loaded and there is no filler prose, but the text is a run-on: the return-field list collides with the benchmark sentence with no punctuation, making it harder to parse. The benchmark citation with date and URL is marginal value for tool selection.

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 correctly compensates by enumerating the returned fields, and it gives a performance profile and endpoint. What remains missing is the behavioral framing (read-only nature, failure modes) needed for an unannotated tool, so it is strong but not complete.

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%, with both the chain and address parameters documented including the default and allowed chain values, so the schema does the heavy lifting. The description adds only the 'Base or another EVM chain' framing, no extra syntax or validation nuance.

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 (Inspect) and resource (ERC-20 on Base or another EVM chain) and enumerates what it returns (name, symbol, decimals, supply, owner, proxy slot, risky selectors), which separates it from chain-specific siblings like the Solana mint auditor. It never names a sibling to contrast against, and the 'risky function selectors' overlap with a token-safety composite tool is left unresolved.

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 only implied by the scope clause: the agent can infer 'use this for EVM token metadata/risk inspection'. There is no explicit when-to-use, when-not-to-use, or reference to alternatives such as the safety composite or price aggregator, leaving the agent to reason from names alone.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools