Skip to main content
Glama

Blockchair

by io.github.pipeworx-io

Pipeworx Trending

pipeworx_trending
Read-onlyIdempotent

What other AI agents are calling on Pipeworx right now. Returns the top tools, top packs, and total call volume over a recent window (24h, 7d, or 30d). Useful for: (1) discovering what data sources are hot for current events, (2) confirming a popular tool is the canonical choice before asking your own question, (3) seeing whether your use case aligns with what most agents need. Self-aggregating signal — derived from CF analytics-engine, no PII, just (pack, tool, count). Cached 5min-1h depending on window.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
windowNo24h (default) | 7d | 30d. Shorter windows surface what's hot right now; longer windows show steady-state demand.

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare readOnly/openWorld/idempotent. Description adds non-obvious behaviors: sourced from CF analytics-engine, no PII, caching 5min-1h, and return shape (pack, tool, count).

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 sentences, each earning its place: purpose, use cases, then aggregation/caching details. Front-loaded with the core function, no fluff.

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, yet description explains return contents and data shape. Also covers caching and aggregation provenance. Complete for a read-only aggregation 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?

Input schema covers window param 100% with enum and per-window semantics. Description only restates the window options without adding new parameter meaning.

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 uses specific verb 'Returns' with resources: top tools, top packs, total call volume. Opens with 'What other AI agents are calling on Pipeworx right now', giving an immediately clear purpose that distinguishes it from sibling discover_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?

Lists three explicit use cases: discovering hot data sources, confirming a canonical tool, and assessing alignment. Provides situational context but doesn't name alternatives or state when-not-to-use.

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

All Blockchair 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
Disambiguation2/5

The major clusters are distinct (blockchain explorer, memory, subscriptions), but several tools have unclear boundaries: ask_pipeworx_beta is currently identical to ask_pipeworx, the three ask_pipeworx variants and deep_research all route questions, and the five Polymarket tools overlap heavily on edge detection. An agent would struggle to pick the right query tool or prediction-market tool without reading very long descriptions.

Naming Consistency2/5

Naming is a mix of single-word nouns (address, block, node, transaction, stats), verb-noun snake_case (validate_claim, generate_llms_txt), and noun-phrase snake_case (entity_profile, bet_research), with no consistent style or verb convention. There is no predictable pattern an agent can generalize from.

Tool Count2/5

36 tools is well above the comfortable range, and most are meta-tools for Pipeworx, Polymarket, memory, and subscriptions rather than Blockchair blockchain functionality. A large share of the count is redundant query and edge-analysis variants, so the size adds confusion rather than capability.

Completeness4/5

As a read-only research and monitoring gateway, the surface is fairly complete: universal routing, grounded answers, entity resolution, profiles, comparisons, claim validation, memory, and subscriptions all have lifecycle coverage. Relative to the Blockchair name, the blockchain side is thin but covers address, block, transaction, node, and stats, with only minor gaps like mempool or raw script details that agents can work around.

Resources