Skip to main content
Glama

Blockscout

by io.github.pipeworx-io

Recent Changes

recent_changes
Read-onlyIdempotent

"What's new with X" / "latest on Y" / "what happened to Z this week / month / quarter" / "updates on Acme" / "news on Tesla recently" / "what's happening with Apple" — change feed for a company in the last N days/weeks/months in ONE parallel call. Fans out to SEC EDGAR (filings since since), GDELT→GNews fallback (news mentions in window — GDELT preferred, GNews when rate-limited or 5xx), USPTO (patents granted; PatentsView API sunset May 2025 so this soft-fails until reactivated). since accepts ISO date ("2026-04-01") or relative shorthand ("7d", "30d", "3m", "1y"). Returns structured changes[] grouped by source + total_changes count + pipeworx:// citation URIs. Use entity_profile instead when you want the static profile (filings + fundamentals + LEI + patents) regardless of window.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeYesEntity type. Only "company" supported today.
sinceYesWindow start — ISO date ("2026-04-01") or relative ("7d", "30d", "3m", "1y"). Use "30d" or "1m" for typical monitoring.
valueYesTicker (e.g., "AAPL") or zero-padded CIK (e.g., "0000320193").

TDQS

A4.9/5.0
Behavior5/5

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

Discloses fan-out to multiple sources with fallback logic (GDELT preferred, GNews when rate-limited/5xx), notes USPTO soft-fail due to API sunset, and describes return structure (changes grouped by source, total_changes count, citation URIs). Annotations already indicate read-only, non-destructive, idempotent; description adds significant behavioral context without contradiction.

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?

Description is information-dense but well-structured: starts with example queries, explains function, parameters, return structure, and alternative tool. Slightly verbose but all sentences earn their place. Could be more concise, but clear and front-loaded.

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 complexity (multiple sources, fallback, date formats, alternative sibling), description is remarkably complete. Covers purpose, parameters, behavior, return values (changes[], total_changes, citation URIs), and when to use alternative. No output schema exists, but description adequately explains output.

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

Parameters5/5

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

Schema coverage is 100%. Description adds meaning beyond schema by explaining since formats (ISO date or relative shorthand with examples like '7d', '30d'), value accepts ticker or CIK, and type only supports 'company'. Enhances understanding for correct invocation.

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?

Description clearly states tool provides a change feed for a company over a time window, aggregating from SEC EDGAR, GDELT/GNews, and USPTO. It gives example queries and distinguishes from entity_profile, which is a sibling tool for static profiles.

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?

Explicitly recommends when to use this tool (change feed) vs entity_profile (static profile). Provides examples of valid since values (ISO dates or relative shorthand) and suggests '30d' or '1m' for typical monitoring.

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