Skip to main content
Glama

NS Pros MCP Gateway

nist-standards__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": "nist-standards__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 supplied, the description carries the full disclosure burden, and it does provide real value: it explains the aggregation source (CF analytics-engine), states there is no PII and the payload is just (pack, tool, count), and mentions caching of 5min-1h. That caching sentence is cut off mid-word ('depending o'), so the freshness guarantee — the single most operationally important behavioral fact here — is left incomplete.

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 lead sentence is well front-loaded and the enumerated use cases are scannable. However, the trailing sentence is truncated ('depending o'), which is a structural defect, and some prose ('seeing whether your use case aligns with what most agents need') is softer than the rest.

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-parameter, no-annotation, no-output-schema read tool, the description covers what is returned, where the numbers come from, privacy posture, and cache behavior. Only the truncated caching clause and the absence of any ordering/shape hint keep it from being fully complete.

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 schema's own enum description already explains that shorter windows surface what's hot while longer ones show steady-state demand. The description merely restates the 24h/7d/30d options without adding new semantics, 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?

The description names a specific verb and resource: it 'returns the top tools, top packs, and total call volume' over a window. That is far more concrete than the bare tool name. It does not, however, distinguish itself from the many sibling `pipeworx_trending` variants or from `ask_pipeworx`, leaving the agent to infer that this is the global/cross-pack view.

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 enumerated use cases give clear positive guidance on when to reach for this tool (discovering hot data sources, confirming a canonical choice, checking alignment with overall demand). There is no when-not guidance and no named alternative such as `ask_pipeworx` for actually querying the data, so it stops short of full routing instructions.

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.