Skip to main content
Glama
Sign In
EVM MCP Server

EVM MCP Server

by mcpdotdirect
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_block_by_number

Retrieve blockchain block details by specifying the block number and network using the EVM MCP Server. Supports Ethereum and other compatible networks for efficient data access.

Instructions

Get a block by its block number

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": {
      "blockNumber": "<blockNumber>"
    },
    "name": "get_block_by_number"
  }
}

Input Schema

NameRequiredDescriptionDefault
blockNumberYesThe block number to fetch
networkNoNetwork name or chain ID. Defaults to Ethereum mainnet.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states the action but lacks behavioral details: it doesn't specify if this is a read-only operation (implied by 'Get'), error handling (e.g., invalid block numbers), performance traits, or rate limits. For a tool with no annotations, this leaves significant gaps in understanding its behavior.

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?

The description is a single, efficient sentence that directly states the tool's purpose without unnecessary words. It's front-loaded and wastes no space, making it easy to parse quickly.

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

Completeness2/5

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

Given no annotations, no output schema, and a simple input schema, the description is incomplete. It doesn't explain what the tool returns (e.g., block data structure), error conditions, or dependencies like network connectivity. For a tool that likely returns complex blockchain data, this lack of context is a significant shortfall.

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 clear parameter descriptions in the schema. The description adds minimal value beyond the schema, as it only mentions 'block number' without elaborating on format or constraints. Since the schema does the heavy lifting, the baseline score of 3 is appropriate, but the description doesn't compensate with additional insights.

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 clearly states the verb ('Get') and resource ('a block'), specifying it's fetched by block number. It distinguishes from siblings like 'get_latest_block' by indicating retrieval via specific number rather than latest. However, it doesn't explicitly differentiate from other block-related tools (none in siblings), so it's not fully sibling-aware.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., network availability), exclusions, or comparisons to siblings like 'get_latest_block' for real-time data. The description is purely functional without contextual advice.

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

Related Tools