Crypto, web, finance and app data tools

EVM Network Info

evm_network_info

Live state of an EVM network: chain ID, latest block number and age, gas price, base and priority fee, block gas use and tx count. Use as a health check before sending transactions.

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

Input Schema

Name	Required	Description	Default
`chain`	No		base

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 23, 2026

TDQS

B3.4/5.0

Behavior3/5

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

No annotations are provided, so the description carries the behavioral-disclosure burden. 'Live state' implies fresh read-only data and the metrics are listed, but it omits auth/rate-limit expectations, error behavior, and caching/freshness guarantees.

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 tightly written sentences: the first front-loads returned metrics, and the second gives a usage context. There is no repetition or filler.

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?

This is a low-complexity read tool with an output schema covering return values, and the description explains what is returned plus a primary use case. It still lacks chain parameter details and sibling routing, so it is not fully complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The single 'chain' parameter has 0% schema description coverage, and the description never names the parameter, its default 'base', or supported chain values. 'An EVM network' only vaguely implies selectability and adds little beyond the schema.

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?

Names a specific resource, the live state of an EVM network, and enumerates returned metrics: chain ID, block number and age, gas price, base/priority fee, gas use, and tx count. It is clear what the tool does, but it does not distinguish itself from overlapping siblings like evm_gas_fees or evm_block.

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?

Provides one usage context: use as a health check before sending transactions. It does not mention when to prefer evm_gas_fees, evm_block, or evm_chain_lookup, nor any exclusions, so 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?