Skip to main content
Glama

NS Pros MCP Gateway

nsf-awards__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": "nsf-awards__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

A4/5.0
Behavior4/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 substantial work: it names the data provenance (CF analytics-engine), states the aggregation grain (pack, tool, count), asserts no PII, and discloses caching of 5min-1h. The caching sentence is truncated mid-word, so the most operationally useful freshness detail is left dangling.

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 payload statement is front-loaded correctly, but the three-item 'Useful for' list is padded relative to the single-window tool, and the final sentence is cut off mid-word ('depending o'), leaving an obviously incomplete thought in the definition body.

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 zero-required-parameter, single-enum read tool with no output schema and no annotations, the description covers what is returned, where it comes from, privacy posture, and caching. The only real shortfall is the truncated cache-duration clause, which slightly undercuts the freshness information an agent would want.

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 enum parameter already documents 24h default, 7d and 30d, including the short-vs-long window tradeoff. The description restates the same three windows without adding format, cost, or combination guidance beyond the schema, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The opening line states a concrete verb and resource - what other agents are calling - and the second sentence specifies the exact return payload (top tools, top packs, total call volume) and the window. An agent can tell this apart from question-answering siblings like ask_pipeworx or tool-discovery siblings without opening the schema.

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, enumerated use cases are given (spotting hot data sources for current events, confirming canonical tool choice, sanity-checking a use case against aggregate demand), which is clear when-to-use context. It stops short of a 5 because no when-not condition or named alternative is offered for cases where a per-tool lookup would be better.

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.