Skip to main content
Glama

Data Providence

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

A5/5.0
Behavior5/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, destructiveHint. Description adds self-aggregating signal from CF analytics, no PII, and caching details (5min-1h). No contradictions.

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?

Concise, front-loaded with key output, then use cases, then technical details. Every sentence is informative with zero redundancy.

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 simple tool (1 param, no output schema, rich annotations), description fully covers what it returns, how to use, caching, and privacy. No gaps.

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?

Single parameter 'window' with enum values. Description adds meaning beyond schema by explaining the trade-off between short and long windows. Schema coverage is 100%.

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 the tool returns trending tools, packs, and call volume over a recent window. It distinguishes itself from siblings by focusing on real-time usage by other AI agents.

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?

Provides three explicit use cases (discovering hot data sources, confirming canonical tool, aligning use case) and guidance on window selection (shorter for hot, longer for steady-state).

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

All Data Providence 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

A4.1/5.0
Disambiguation3/5

Most tools have distinct purposes, but several clusters overlap: ask_pipeworx vs ask_pipeworx_beta are currently functionally identical, polymarket_arbitrage / polymarket_edges / polymarket_kalshi_spread all hunt mispricings via different mechanisms, ai_visibility_check is wrapped by scan_competitor_ai_presence, and discover_tools vs suggest_questions both serve tool discovery. The rich descriptions mitigate but do not eliminate misselection risk.

Naming Consistency4/5

Names are all snake_case and follow recognizable conventions: verb_noun for actions (compare_entities, resolve_entity, validate_claim), domain-prefixed families (polymarket_*, pipeworx_*, recent_*, ask_pipeworx_*), and a few bare verbs (remember, recall, query). Minor deviations like bet_research (noun_verb) and noun-only names (datasets, metadata) break the pattern, but the overall scheme is predictable.

Tool Count2/5

At 34 tools, this exceeds the 25+ threshold for 'too many' and bundles several distinct domains — general data querying, prediction markets, AI visibility, memory, subscriptions, open data, and npm auditing — into one server. The breadth is defensible for a data platform, but the agent-facing surface is sprawling and would benefit from splitting into focused servers.

Completeness4/5

The core data workflow is well covered: discover (discover_tools, suggest_questions), resolve (resolve_entity), query (ask_pipeworx), ground (ask_pipeworx_grounded, validate_claim), research (deep_research), compare (compare_entities), profile (entity_profile), and changes (recent_changes). Prediction markets, memory, and subscriptions each have full lifecycles. The main gap is no tool for fetching returned pipeworx:// citation URIs directly, plus a few soft-failing sources.

Resources