Skip to main content
Glama

NS Pros MCP Gateway

noaa-ncei__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-ncei__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 does real work: it names the data source (CF analytics-engine), states no PII is returned, discloses the tuple shape (pack, tool, count), and gives a cache TTL of 5min-1h. However, the final sentence is cut off mid-word ("depending o"), so the caching caveat is incomplete, and there is no statement about auth, rate limits, or whether counts are global or per-pack.

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 one-line purpose, then return contents, then a scannable numbered use-case list, then provenance. Nothing is redundant, though the three-item use-case list is a little padded for a single-parameter read tool. The truncated trailing sentence is a structural defect worth fixing.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-optional-param, no-output-schema, no-annotation tool, the description covers purpose, return shape, and data provenance adequately. It still leaves open the scope question (global vs. pack-specific), the truncation on caching, and any freshness caveat an agent would need to interpret a ranking. Those gaps keep it at minimum-viable-plus.

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 window parameter already carries an enum with per-value explanation, so the schema does the heavy lifting. The description only restates the available windows (24h, 7d, 30d) without adding format or default behavior beyond what the schema says. 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?

A concrete verb and resource: "Returns the top tools, top packs, and total call volume over a recent window". That tells an agent exactly what comes back, and it is distinguishable from ask_pipeworx-style siblings because it is an aggregate ranking rather than a query. It never states whether the ranking spans all of Pipeworx or only the noaa-ncei pack, which leaves one scoping question open.

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 use cases are given: finding hot data sources for current events, confirming a popular tool is canonical, and checking alignment with what most agents need. That is genuine when-to-use guidance rather than implied usage. No when-not-to-use or explicit alternative is stated, so it stops 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.