Skip to main content
Glama
Sign In
MCP GetBlock Server

MCP GetBlock Server

Official
by GetBlock-io
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

get-latest-blocks

Retrieve recent blockchain blocks for Ethereum or Solana, specifying the number of blocks to fetch via GetBlock.io API.

Instructions

Get information about recent blocks

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": "get-latest-blocks"
  }
}

Input Schema

NameRequiredDescriptionDefault
countNoNumber of recent blocks to fetch
chainNoBlockchain network (e.g., eth, solana)eth

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?

With no annotations, the description should disclose behaviors like non-destructiveness, data freshness (what 'recent' means), and possible rate limits. It only provides a vague purpose statement.

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 concise sentence with no fluff. It is appropriately front-loaded but lacks structured details like parameter clarification.

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 output schema, the description should at least hint at the return format (e.g., list of block objects). It fails to explain what 'recent' means or how results are ordered, making it incomplete for a tool with optional parameters.

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 descriptions cover both parameters fully (count and chain with defaults). The description adds no additional meaning beyond what the schema provides, so baseline of 3 is appropriate.

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 tool gets information about recent blocks, which is specific enough given the sibling tools focus on different aspects like chain info or gas price. However, it could be more precise about what information is returned.

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 on when to use this tool vs alternatives like get-chain-info. The description does not provide any context for appropriate use cases.

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