Skip to main content
Glama

NS Pros MCP Gateway

nj-mvc__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": "nj-mvc__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 burden and does reasonably well: it discloses provenance (CF analytics-engine), that the data is PII-free and shaped as (pack, tool, count), and that responses are cached 5min–1h. The cache sentence is cut off mid-word, leaving the freshness contract incomplete, and there is no statement about auth or rate limits.

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?

The lead sentence front-loads what the agent gets, and the numbered use cases scan quickly. It runs slightly long for a one-parameter read tool, and the final clause is truncated, which wastes a sentence that should have earned its place.

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?

For a single optional-enum parameter with no output schema and no annotations, the description covers return shape (top tools, top packs, volume), provenance, privacy, and caching — nearly everything needed to call it correctly. The truncated caching note is the only material gap.

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 `window` parameter already enumerates 24h/7d/30d with its own trade-off explanation, so the description's restatement of the window options adds nothing new. Baseline 3 is appropriate when the schema does the heavy lifting on a one-parameter tool.

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?

"Returns the top tools, top packs, and total call volume over a recent window" gives a specific verb and concrete resources, and the opening line frames it as an aggregate-demand signal rather than a search tool. It does not explicitly distinguish itself from siblings like discover_tools or ask_pipeworx, so the agent must infer the boundary.

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 numbered use cases (spotting hot data sources, sanity-checking a canonical choice, comparing your use case to aggregate demand) tell the agent exactly when to reach for it. Missing is any when-not guidance or a named alternative for cases where trending is the wrong signal.

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.