Skip to main content
Glama

Manifold

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 declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint. The description adds valuable detail: data source ('CF analytics-engine'), privacy ('no PII'), and caching behavior ('5min-1h'). No contradiction.

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 succinct bullet list. Every sentence is necessary, front-loaded with the main action, and free of redundancy or 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?

For a simple tool with one optional parameter and no output schema, the description fully explains the return format, data source, caching, and privacy. No gaps remain for effective use.

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% with enum and description. The tool description adds interpretive value ('Shorter windows surface what's hot right now; longer windows show steady-state demand'), going beyond the schema definition.

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 specifies a clear verb ('Returns') and defines the resource ('top tools, top packs, and total call volume'), with scope ('recent window'). It is distinct from sibling tools, which include search and discovery tools, making the purpose unambiguous.

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, confirming canonical tool, aligning use case), but no when-not-to-use or alternatives are mentioned. The context is clear, but exclusions would improve guidance.

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

All Manifold 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/5.0
Disambiguation3/5

Tools have distinct purposes but some overlap exists, e.g., multiple ask_pipeworx variants and deep_research could confuse an agent. Prediction market tools are differentiated but not immediately obvious.

Naming Consistency3/5

Names are consistently in snake_case but mix verb and noun orders (e.g., 'ai_visibility_check' vs 'ask_pipeworx'). No strict verb_noun pattern throughout.

Tool Count3/5

34 tools is on the high side but still reasonable given the broad domain coverage. Some tools could be consolidated without loss.

Completeness4/5

Covers data querying, company research, prediction markets, subscriptions, and memory. Minor gaps like no direct web search but ask_pipeworx substitutes.

Resources