Skip to main content
Glama

Blockscout

by io.github.pipeworx-io

Scan Dependency

scan_dependency
Read-onlyIdempotent

Composite "should I add this npm package to my project" check in ONE call — fans out across deps.dev (license + advisories + version history) and bundlephobia (gzipped/minified bundle size, dependency count, ESM/tree-shake support). Use whenever an agent asks "is X safe / popular / small" or "what does adding lodash cost me". Returns a summary block (is_latest, license, published_at, advisory_count, bundle_kb_min, bundle_kb_gz, dependency_count, has_esm, tree_shakeable), per-advisory detail, links, and a list of recent alternative versions. NPM ecosystem only in v1; PyPI / Maven / Cargo / Go fall under deps.dev:version directly. Partial failures degrade gracefully — bundlephobia's first measurement on a new version can take 5-30s; sources_failed will list it if it times out, the rest still returns.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
packageYesnpm package name. Scoped packages (e.g. "@types/node") are accepted.
versionNoSpecific version to check (e.g., "18.3.1"). Defaults to the latest published version when omitted.

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already provide readOnlyHint, openWorldHint, idempotentHint, destructiveHint false. Description adds valuable context about partial failures, bundlephobia latency (5-30s), graceful degradation, and sources_failed.

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 relatively long but well-structured and front-loaded with key information. Every sentence adds value, though a very slight reduction in length could improve conciseness.

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?

No output schema, but the description thoroughly explains the return structure (summary block, per-advisory details, links, alternative versions). Also covers NPM-only scope and graceful degradation, making the tool self-contained.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema has 100% coverage for both parameters. Description adds context about scoped packages and version defaulting to latest, which improves over schema alone but is not extensive.

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's function as a composite check for npm packages, combining deps.dev and bundlephobia. It distinguishes from siblings by specifying 'NPM ecosystem only in v1' and mentions alternatives like deps.dev:version.

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

Usage Guidelines5/5

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

Explicit usage guidance: 'Use whenever an agent asks "is X safe / popular / small" or "what does adding lodash cost me".' Also specifies NPM-only and notes fallback for other ecosystems.

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

All Blockscout 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

B3.3/5.0
Disambiguation1/5

The tool set includes multiple overlapping tools for predictions (bet_research, polymarket_arbitrage, polymarket_edges, etc.) and data lookups (ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded), and mixes blockchain tools with unrelated services, making it difficult for an agent to select the correct tool.

Naming Consistency1/5

Tool names follow no consistent pattern: some use verb_noun (get_address, list_chains), others are multi-word phrases (ai_visibility_check, compare_entities), and styles mix snake_case and camelCase erratically.

Tool Count2/5

With 39 tools, the surface is bloated for a blockchain explorer. Many tools are unrelated to blockchain, inflating the count well beyond what is necessary for the server's stated purpose.

Completeness1/5

The server is named 'Blockscout' but includes mostly non-blockchain tools, leaving the blockchain domain severely incomplete. Even the blockchain-specific tools miss common operations like event logs or internal transactions.

Resources