Skip to main content
Glama

NS Pros MCP Gateway

noaa-ndbc__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": "noaa-ndbc__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?

No annotations are supplied, so the description carries the full burden. It does disclose useful traits: self-aggregating signal from CF analytics-engine, no PII, payload shape (pack, tool, count), and caching of 5min-1h. However, the caching sentence is truncated mid-word ('depending o'), and there is no mention of rate limits, auth, or failure behavior.

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?

Front-loaded with the core statement, and the numbered use cases are scannable. But the closing metadata sentence runs on and is cut off ('Cached 5min-1h depending o'), which is a real structural defect in a definition this short.

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 read tool with no output schema, the description covers what it returns (pack, tool, count), the aggregation source, caching, and privacy. The truncated tail is the only meaningful 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 description coverage is 100% and the single window parameter is fully documented with its enum and default in the schema. The description adds only a light gloss ('24h, 7d, or 30d') that largely restates the schema, so the baseline applies rather than a bonus.

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+resource: returns top tools, top packs, and total call volume over a recent window. That is concrete enough for an agent to know what comes back. It does not differentiate itself from the ask_pipeworx siblings that also serve this namespace, so it falls short of a 5.

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?

Enumerates three explicit use cases (discovering hot data sources for current events, confirming canonical tool choice, sanity-checking your use case against demand). Clear context for when to reach for it, but no when-not guidance and no named alternative for actually answering a data question, which ask_pipeworx presumably covers.

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.