Skip to main content
Glama

NS Pros MCP Gateway

nvd__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": "nvd__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

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does add real behavioral context: the data is self-aggregating from CF analytics-engine, contains no PII, returns only (pack, tool, count), and is cached between 5 minutes and 1 hour. What is missing is any statement about rate limits, result-set size, or how the top-N cutoff is chosen.

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

Conciseness4/5

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

Front-loads the core signal in one sentence and then numbers the use cases, which is easy to scan. It is docked because the final sentence is truncated mid-word ('Cached 5min-1h depending o'), leaving an unfinished thought in the text an agent actually receives.

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?

There is no output schema, so the description must convey return values, and it does: top tools, top packs, total call volume, and the (pack, tool, count) record shape. Combined with the single optional parameter and 100% schema coverage, that covers what an agent needs, short of the truncated caching sentence.

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 coverage is 100% and the single enum parameter is fully documented in the schema, so the description only needs to reinforce meaning. It does name the three windows and frames shorter as 'hot right now' versus longer as steady-state demand, but that framing largely duplicates the schema text, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: reports which tools other AI agents call on Pipeworx, returning top tools, top packs, and total call volume over a time window. That is concrete enough to distinguish it from a single-source query, though it never contrasts itself with the many per-source *__pipeworx_trending siblings, leaving the global-vs-scoped distinction to inference.

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 explicit when-to-use cases (discovering hot data sources, confirming a popular tool is canonical, checking alignment with agent demand), which is stronger than most definitions. It offers no when-not-to-use guidance or named alternative when the agent needs a specific source's trend rather than the aggregate.

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.