Skip to main content
Glama

Blockstream Info

by io.github.pipeworx-io

Compare Entities

compare_entities
Read-onlyIdempotent

"Compare X and Y" / "X vs Y" / "X versus Y" / "which is bigger / better / larger / more profitable" / "rank these companies" / "head to head" — side-by-side comparison of 2–5 companies or drugs in ONE parallel call. ALWAYS PREFER over sequential single-pack lookups when comparing entities. type="company" pulls LATEST 10-K revenue + net income + cash + long-term debt from SEC EDGAR/XBRL (off-calendar fiscal years handled correctly — AAPL Sep, NVDA Jan, etc.). type="drug" pulls FAERS adverse-event counts, FDA approval counts, active trial counts. Results sorted by primary metric so "largest" / "most" / "biggest" reads off the top of the response. Returns paired data + pipeworx:// citation URIs per entity. Replaces 8–15 sequential lookups.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeYesEntity type: "company" or "drug".
valuesYesFor company: 2–5 tickers/CIKs (e.g., ["AAPL","MSFT"]). For drug: 2–5 names (e.g., ["ozempic","mounjaro"]).

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

The description adds behavioral context beyond annotations: it makes a parallel call, handles off-calendar fiscal years, sorts results by primary metric, and returns citation URIs. Annotations already provide readOnly/idempotent/etc., and description aligns fully.

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 dense but every sentence adds value: front-loaded with examples, then specifics on data sources, sorting, and efficiency. No wasted words; 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?

Despite no output schema, the description explains return format ('paired data + pipeworx:// citation URIs') and sorting. For a tool with two entity types, it covers all key aspects: data sources, parallel execution, and result structure.

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 coverage is 100%, baseline 3. The description adds meaning by explaining what data each type pulls (SEC EDGAR/XBRL for company, FAERS for drug) and that values are tickers or drug names, going beyond schema descriptions.

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 states the tool does side-by-side comparison of 2-5 companies or drugs, with specific verb 'compare' and examples like 'X vs Y'. It clearly distinguishes from sibling tools like entity_profile and sequential lookups.

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 explicitly says 'ALWAYS PREFER over sequential single-pack lookups when comparing entities' and 'Replaces 8–15 sequential lookups', providing clear when-to-use guidance. It does not explicitly list when not to use, but context implies alternatives for single entity lookups.

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

All Blockstream Info 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.1/5.0
Disambiguation1/5

The tool set includes multiple near-identical tools (ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded) and several overlapping entity/profile tools (entity_profile, compare_entities, resolve_entity, validate_claim) that make it hard for an agent to choose the right one. The Bitcoin-specific tools are isolated and don't integrate well with the rest, creating two separate domains.

Naming Consistency2/5

Naming conventions are mixed: some tools use snake_case (ask_pipeworx, fee_estimates), some use underscores (polymarket_edges), and others are standalone verbs (remember, recall, forget). No consistent pattern is followed across the tool set.

Tool Count2/5

With 39 tools, the server is overstuffed for its stated purpose ('Blockstream Info'). The Bitcoin blockchain tools are only 7, while the rest are a sprawling external data platform (Pipeworx) with many redundant tools, making the number feel excessive and unfocused.

Completeness2/5

For a Bitcoin-oriented server, the blockchain tools cover basic operations (address, block, transaction, fee_estimates) but miss essentials like UTXO queries or block details. Meanwhile, the Pipeworx tools dominate and are overcomplete for a server that should be lightweight. The mismatch leaves the Bitcoin part incomplete.

Resources