Skip to main content
Glama

mcp-server

by com.blockscout

Direct Blockscout API Call

direct_api_call
Read-only

Call a raw Blockscout API endpoint for advanced or chain-specific data.

Before the first call to this tool in a session, read
`blockscout-mcp://skill/SKILL.md` (the operating rules), then
`blockscout-mcp://skill/references/blockscout-api-index.md` (the authoritative
index of callable endpoints); skip both reads only if this skill content is
already in context. Recalled Blockscout API knowledge is not a substitute:
endpoint paths, parameters, and response shapes vary across Blockscout
versions and per-chain deployments.

Supports POST requests with a JSON body for endpoints like JSON RPC.

**SUPPORTS PAGINATION**: If response includes 'pagination' field,
use the provided next_call to get additional pages (GET only).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cursorNoThe pagination cursor from a previous response to get the next page of results.
methodNoHTTP method used for the upstream call. Use POST with json_body.GET
chain_idYesThe ID of the blockchain
json_bodyNoJSON request body for POST requests.
session_idNoOpaque session identifier.
query_paramsNoOptional query parameters forwarded to the Blockscout API.
endpoint_pathYesThe Blockscout API path to call (e.g., '/api/v2/stats'); do not include query strings — pass all query parameters via query_params to avoid double-encoding.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataYesThe main data payload of the tool's response.
notesNoA list of important contextual notes, such as warnings about data truncation or data quality issues.
paginationNoPagination information, present only if the 'data' is a single page of a larger result set.
content_textNoOptional human-readable summary used for MCP content responses.
instructionsNoA list of suggested follow-up actions or instructions for the LLM to plan its next steps.
data_descriptionNoA list of notes explaining the structure, fields, or conventions of the 'data' payload.

TDQS

A4.4/5.0
Behavior5/5

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

The description adds substantial behavioral context beyond the annotations: it requires reading skill files as a prerequisite, explains pagination mechanics via the 'pagination' field and next_call (GET only), supports POST for JSON RPC, and warns that endpoint paths/parameters vary per chain. This is rich, non-obvious behavior that helps correct invocation and expectations.

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 moderately long (4 sentences plus a pagination note) but every sentence carries necessary information: purpose, prerequisite reads, POST support, and pagination. It is front-loaded with the purpose and structurally clear, though slightly dense. A tight, perfectly minimal version might be a 5, but this is appropriately sized for the tool's complexity.

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

Completeness5/5

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

Given the tool's complexity (7 params, generic raw access, many siblings) and the presence of an output schema, the description covers all critical aspects: purpose, prerequisites, method flexibility, pagination, and cross-version variability. It leaves no major gap for the agent to safely use the tool.

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%, so the baseline is 3. The description itself does not add new parameter semantics beyond what the schema already provides (e.g., endpoint_path's no-query-string rule, cursor pagination, POST with json_body are all in the schema descriptions). It neither compensates nor undercuts.

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 opens with 'Call a raw Blockscout API endpoint for advanced or chain-specific data'—a specific verb and resource. The word 'raw' clearly distinguishes this generic tool from the specialized sibling tools, and 'advanced or chain-specific data' signals that it covers cases beyond the specialized tools.

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

Usage Guidelines4/5

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

The description gives clear context: 'for advanced or chain-specific data' implies use when specialized tools are insufficient. It also mandates reading skill files before first use, which is a strong usage guideline. However, it does not explicitly name alternatives or state 'use this instead of X', so it gets a 4 rather than a 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All mcp-server toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.1/5.0
Disambiguation5/5

Each tool targets a distinct blockchain resource or action (address, block, transaction, token, NFT, contract, chain, raw API, session init). Even though direct_api_call is a generic fallback, the specialized tools have clear, non-overlapping purposes, and the complementary nature of tools like get_token_transfers_by_address and get_transactions_by_address is explicitly documented.

Naming Consistency4/5

The majority of tools follow a consistent get_<resource> pattern (e.g., get_block_info, get_tokens_by_address), but there are notable deviations: direct_api_call, lookup_token_by_symbol, inspect_contract_code, read_contract, and __unlock_blockchain_analysis__. These verbs are still descriptive and readable, but the mix of 'get' with other verbs prevents a perfect 5.

Tool Count4/5

With 16 tools, the server is slightly above the ideal 3-15 range but not excessive. Each tool maps to a significant Blockscout API capability, and the count feels proportional to the breadth of blockchain data covered. It is heavier than a minimal toolkit but not bloated.

Completeness4/5

The tool set covers core exploration workflows: address info, block lookup, transaction details, token/NFT holdings, contract ABI/source inspection, and read-only contract calls. Minor gaps like a dedicated token-info-by-contract-address tool exist, but the direct_api_call fallback and get_address_info's token details mitigate these. The surface is comprehensive for a read-only blockchain explorer.

Resources