Crypto, web, finance and app data tools

EVM Chain Lookup

evm_chain_lookup

Look up any EVM chain by chain ID or name (8453, base, arbitrum): chain ID in decimal and hex, native currency, public RPC URLs, block explorers and testnet flag. Use to configure wallets, RPCs or cross-chain apps.

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": {
      "q": "<q>"
    },
    "name": "evm_chain_lookup"
  }
}

Input Schema

Name	Required	Description	Default
`q`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 22, 2026

TDQS

A3.7/5.0

Behavior3/5

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

No annotations, so the description must carry the behavioral burden. It does disclose the full return payload (chain IDs, currency, RPCs, explorers, testnet flag), which signals a static read-only reference lookup. It does not state that the data is static/cached, whether RPC URLs are live or checked, or anything about rate limits or freshness.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with the capability and return fields, with the use case trailing. The parenthetical examples are dense but earn their place by pinning down the input format.

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?

A one-parameter read-only lookup with an output schema present, so return values need not be re-explained and the description's field list is a bonus. The remaining gap is sibling disambiguation versus evm_network_info / chains_tvl, which the description never resolves.

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?

The single 'q' parameter has 0% schema description coverage, but the description compensates by explaining it accepts a chain ID or a name and giving concrete examples ('8453, base, arbitrum') plus the note that IDs can be decimal or hex. Only ambiguity resolution (name vs ID collisions, case sensitivity) is unaddressed.

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 ('look up any EVM chain') and enumerates exactly what comes back: decimal/hex chain ID, native currency, RPC URLs, explorers, testnet flag. That is far more informative than the title alone. It does not, however, distinguish itself from the very similar sibling evm_network_info, which an agent would have to disambiguate on its own.

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?

'Use to configure wallets, RPCs or cross-chain apps' gives a use case, which implies when the tool is relevant, but never states when NOT to use it or which sibling to prefer for overlapping chain/network data. Guidance is implied rather than explicit.

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

All Crypto, web, finance and app data tools tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?