Skip to main content
Glama

Hdx

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.6/5.0
Behavior5/5

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

The description adds significant context beyond annotations: it reveals the data source (CF analytics-engine), privacy guarantees (no PII), and caching behavior (5min-1h). This complements the readOnlyHint and idempotentHint already present.

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?

Every sentence adds value: it defines output, enumerates use cases, explains data source and caching. No filler, front-loaded with the key result. Ideal length for the complexity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple tool with one optional parameter and no output schema, the description covers what is returned (top tools, top packs, total call volume) and the time windows. It could specify the structure of the response (e.g., sorted lists with counts), but the information is sufficient for an agent's decision.

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?

The schema already describes the parameter fully (enum values, default). The description adds usage guidance on window selection (short vs long windows) and reinforces the default, which goes beyond the schema.

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 what the tool returns (top tools, top packs, total call volume) with a specific verb and resource. It distinguishes itself from sibling tools by focusing on trending/aggregate data rather than direct answers or search.

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 lists three specific use cases (discovering hot data sources, confirming canonical tool, aligning needs) but does not explicitly state when not to use it or compare to alternatives. The context is clear enough for an agent to decide.

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

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

A3.8/5.0
Disambiguation2/5

Multiple tools have overlapping purposes (e.g., three variants of ask_pipeworx, several polymarket tools, and multiple discovery/entity tools). Despite detailed descriptions, the similiar functionalities create confusion for an agent selecting among them.

Naming Consistency3/5

Tool names are consistently in snake_case but the verb/noun pattern is mixed: some start with verbs (ask_, list_, remember_), others with nouns (entity_profile, polymarket_edges). This inconsistency reduces predictability.

Tool Count2/5

35 tools is high for a single server, especially when the scope spans two disparate domains (HDX humanitarian data and Pipeworx data platform). Many tools could be logically split into separate, more focused servers.

Completeness3/5

The tool set covers a wide range of functionality (data retrieval, comparison, monitoring, memory) but has notable gaps: no direct data download tool for HDX resources, no account management, and no exploration of Pipeworx packs beyond discover_tools.

Resources