Skip to main content
Glama

NS Pros MCP Gateway

nsi-bg__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": "nsi-bg__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.6/5.0
Behavior3/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 value: it says the data is self-aggregating from a CF analytics-engine, contains no PII, is shaped as (pack, tool, count), and is cached 5min-1h. However, the caching sentence is cut off mid-word ('depending o'), leaving the cache behavior incomplete, and nothing is said about ranking order or freshness of the underlying aggregation.

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?

The core fact and the use cases are front-loaded and easy to scan, but the final sentence is truncated mid-word, which is a real defect in a short description, and the three 'useful for' items overlap somewhat (hot vs canonical vs alignment).

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 one-optional-param read tool with no output schema, the description is nearly sufficient: it names the returned dimensions, states the aggregation source and the absence of PII, and gives the caching range. The only gap is the truncated cache statement and the unstated sort/limit of 'top' results.

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% with an enum on the single window parameter, so the schema already documents allowed values and defaults. The description restates the 24h/7d/30d framing and adds a light intuition about short vs long windows, but that intuition duplicates the schema's own parameter description rather than extending it.

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?

Opens with a specific framing and states concretely that it returns top tools, top packs, and total call volume over a selected window. A reader knows exactly what comes back, though it never names a sibling (e.g. discover_tools) to differentiate itself from tools that also surface tools.

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?

Provides three explicit numbered use cases: discovering hot data sources for current events, confirming a popular tool is canonical, and gauging use-case alignment. It gives clear positive context but no exclusions or 'use X instead when...' routing against the sibling tools.

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.