Skip to main content
Glama

Ship On Friday

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

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

Annotations already include readOnlyHint, openWorldHint, etc. Description adds valuable context: derived from CF analytics-engine, no PII, caching behavior, and response structure.

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?

Two sentences plus a bullet list. Front-loaded with a hook (‘What other AI agents are calling...’). No wasted words; 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?

Given one parameter and no output schema, description explains what is returned (top tools, packs, call volumes) and caching behavior, making it fully informative.

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?

Single parameter with full schema coverage. Description adds value by explaining that shorter windows surface hot items and longer windows show steady-state demand.

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 clearly states it returns trending tools, packs, and call volume over a window, distinguishing it from siblings like discover_tools by focusing on current popularity.

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?

Three explicit use cases are provided (discovering hot data sources, confirming canonical tool, aligning use case). No when-not or alternatives are mentioned, but context is clear.

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

All Ship On Friday 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.3/5.0
Disambiguation4/5

Most tools have clearly distinct purposes, but there is some overlap among data query tools like ask_pipeworx, ask_pipeworx_grounded, deep_research, entity_profile, compare_entities, and recent_changes. However, detailed descriptions and different use cases help an agent distinguish them, so it is mostly clear.

Naming Consistency5/5

All tool names follow a consistent lower_snake_case pattern with a verb_noun style (e.g., ask_pipeworx, list_subscriptions, validate_claim). There are no mixed conventions, making it predictable and easy to understand.

Tool Count4/5

With 31 tools, the server covers a broad domain of data queries, prediction markets, memory, and subscriptions. While slightly more than typical, each tool earns its place and the count is reasonable for the comprehensive platform scope.

Completeness5/5

The tool surface is extensive, covering data querying, analysis, entity resolution, comparison, change tracking, memory, subscriptions, and more. There are no obvious gaps; it supports a wide range of user intents for the server's purpose.

Resources