Skip to main content
Glama

Blockstream Info

by io.github.pipeworx-io

Search Within a Source

search_within
Read-onlyIdempotent

Semantic search INSIDE a fetched record. Pass the text you already pulled (e.g. a SEC 10-K body, an article, a long tool result) plus a natural-language query; get back the top-N passages with character offsets and similarity scores. Use when the record is too big to cram into the prompt — search_within saves context, returns only the passages that matter, and every passage carries an offset so the agent can verify a verbatim quote. Pairs with ask_pipeworx_grounded: fetch with the gateway, ground over the relevant passages instead of the whole document. BGE-base-en embeddings + cosine over 500-char overlapping windows; cap is 200K chars (longer inputs are truncated and flagged).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
textYesThe document text to search inside (max ~200K chars).
limitNoMax passages to return (1-20, default 5).
queryYesNatural-language query — what passages do you want? E.g. "supply-chain risk", "fiscal year 2024 revenue", "drug interactions with warfarin".

Schema Changelog

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

  1. Added

TDQS

A4.9/5.0
Behavior5/5

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

Description adds beyond annotations: explains that passages carry offsets for verification, technical details on embeddings (BGE-base-en, cosine, 500-char windows), and 200K char cap with truncation. No contradiction with annotations.

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?

Three dense sentences with no clutter. Front-loaded with purpose and key benefit, following with technical specifics. Every sentence earns its place.

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, description covers return values (passages with offsets and similarity scores), edge case (truncation), and pairing guidance. Complete for a 3-param tool.

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%, so baseline 3. Description adds value with examples for query, defaults for limit, and explanation of embedding model and window size. Slightly above baseline.

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 specifies 'semantic search INSIDE a fetched record' with clear verb and resource. Distinguishes from siblings by mentioning pairing with ask_pipeworx_grounded and context-saving benefit.

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 when-to-use: 'Use when the record is too big to cram into the prompt.' Provides alternative: 'fetch with the gateway, ground over the relevant passages instead of the whole document.'

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