Skip to main content
Glama

NS Pros MCP Gateway

nobel__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": "nobel__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 supplied, the description carries the full disclosure burden and does reasonably well: it names the provenance (self-aggregating signal from CF analytics-engine), states 'no PII', describes the record shape as (pack, tool, count), and gives a cache window of 5min-1h. The caching sentence is cut off mid-word, so the exact caching rule and any freshness caveats are lost.

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-loaded with the core definition and the return payload before the use-case list, and every sentence carries signal. The trailing cache sentence is truncated mid-word ("depending o"), leaving visibly unfinished text that weakens polish.

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?

No output schema exists, so the description must describe returns, and it does at a high level (top tools, top packs, total call volume, tuple shape). The truncation leaves the caching/freshness behavior incomplete, which matters for a time-windowed analytics tool where staleness affects interpretation.

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 enum parameter already documents the 24h/7d/30d tradeoff explicitly, so the description adds nothing beyond restating the window options. Baseline 3 applies when the schema does the work.

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 resource (trending/call-volume data on Pipeworx) and enumerates the returned artifacts: top tools, top packs, and total call volume. A verb is implicit ("returns") rather than a crisp action verb, and the description never clarifies the per-source scoping implied by the 'nobel__' prefix in the tool name, so an agent could read it as a global leaderboard rather than a source-specific one.

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 numbered use cases give concrete when-to-use context: discovering hot data sources, confirming a tool is canonical before querying, and benchmarking one's own use case. There are no explicit exclusions or named alternatives for when trending data is the wrong signal, which keeps it short of a 5.

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.