Skip to main content
Glama

NS Pros MCP Gateway

numverify__pipeworx_trending

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 o

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "window": "7d"
    },
    "name": "numverify__pipeworx_trending"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

No annotations exist, so the description carries the full burden, and it does substantial work: it discloses caching ('Cached 5min-1h'), provenance ('derived from CF analytics-engine'), privacy posture ('no PII'), and the aggregate tuple '(pack, tool, count)'. The caching sentence is cut off mid-word ('depending o'), leaving the actual staleness behavior ambiguous, which keeps this below a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is front-loaded with the core behavior, which is good, but the tail is bloated with marketing-flavored phrasing ('Self-aggregating signal') and ends in a truncated sentence, which reads as an editing defect rather than a deliberate stop.

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?

With no output schema, the description must describe returns, and it does: top tools, top packs, total call volume, shaped as (pack, tool, count). Provenance and caching are also covered. The incomplete caching detail is the only meaningful hole for a low-complexity, single-optional-param read 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?

Schema description coverage is 100% and the single parameter already carries the 24h/7d/30d enum with its own explanation of short-vs-long window tradeoffs. The description only repeats the three window values, adding no new meaning, so the baseline of 3 applies.

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?

States a specific resource and concrete payload: 'top tools, top packs, and total call volume over a recent window (24h, 7d, or 30d)'. An agent knows exactly what it gets back and at what granularity, without needing to open the schema.

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?

Gives three enumerated use cases: discovering hot data sources for current events, confirming a popular tool is canonical, and checking use-case alignment. This is clear positive guidance, but there is no when-not-to-use guidance and no named alternative for related needs (e.g. per-source popularity vs. global popularity).

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.