Skip to main content
Glama
Sign In
Alchemy MCP Server

Alchemy MCP Server

Official
by alchemyplatform
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Remote

getBeaconBlockAttestations

Retrieve attestations included in a Beacon Chain block by providing a block ID (head, genesis, finalized, slot number, or block root). Specify the network to fetch attestation data for analysis.

Instructions

Get attestations included in a specific Beacon Chain block

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": {
      "blockId": "<blockId>"
    },
    "name": "getBeaconBlockAttestations"
  }
}

Input Schema

NameRequiredDescriptionDefault
networkNoNetwork ID. Call listSupportedNetworks for all options. e.g. "eth-mainnet", "base-mainnet"eth-mainnet
blockIdYesBlock ID: head, genesis, finalized, slot number, or 0x-prefixed block root

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.5

TDQS

A3.5/5.0
Behavior2/5

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

No annotations provided, so the description carries full burden. It only states the basic function, with no mention of read-only behavior, error states, or any side effects. This is insufficient for an unannotated tool.

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, direct sentence that front-loads the action. Every word is necessary, no fluff.

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?

The setup is simple (2 parameters, no output schema), but the description could mention the format or structure of the returned attestations. Without that, an agent might lack understanding of what to expect.

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 coverage is 100%, with both parameters described adequately. The description does not add any additional meaning beyond the schema; it simply restates the tool's purpose. Baseline score of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool retrieves attestations for a specific Beacon Chain block. The name and description align well, and among many getBeacon* sibling tools, this one is distinct for attestations.

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?

No explicit guidance on when to use this tool vs alternatives like getBeaconPoolAttestations or getBeaconBlock. The description implies its use for block-specific attestations but does not contrast with siblings.

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