Crypto, web, finance and app data tools

EVM Block

evm_block

An EVM block by number or tag (latest, finalized, safe): hash, parent, time, miner, gas used and limit, base fee, size and its transaction hashes.

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_block"
  }
}

Input Schema

Name	Required	Description	Default
`block`	No		latest
`chain`	No		ethereum

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 23, 2026

TDQS

B3/5.0

Behavior2/5

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

No annotations are provided, so the description must carry full behavioral burden. It lists returned fields but omits crucial behavioral details: it doesn't mention the default 'latest' block, the 'chain' parameter and its default, error handling for invalid blocks, or whether the operation is read-only (though implied). This leaves significant gaps for a tool with no annotations.

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?

The description is a single, front-loaded sentence that efficiently conveys the tool's purpose and return fields without unnecessary words. It could be marginally improved with slight structure (e.g., explicitly noting the chain parameter), but it is appropriately sized.

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?

An output schema exists, so the description needn't explain return values, yet it does list fields (which is redundant but harmless). However, it fails to cover the 'chain' parameter and its default, and lacks behavioral context like default block selection or error conditions. It is adequate but incomplete for a tool with no annotations and 0% schema coverage.

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?

Schema description coverage is 0%, so the description must compensate. It partially clarifies the 'block' parameter by explaining it accepts a number or specific tags (latest, finalized, safe), but it entirely ignores the 'chain' parameter, leaving half of the parameters undocumented.

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?

The description states a specific verb+resource: 'An EVM block by number or tag', and lists the fields returned. This clearly distinguishes it from most siblings, though it does not explicitly name alternatives or contrast with tools like evm_network_info or evm_transaction_status.

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 phrase 'by number or tag' and the enumerated tags (latest, finalized, safe), but there is no explicit guidance on when to use this tool versus other block-related or chain-related siblings, nor any mention of prerequisites or exclusions.

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?