Skip to main content
Glama

NS Pros MCP Gateway

noaa-ncei__suggest_questions

What can I ask Pipeworx? / what is Pipeworx good for? / what can you do? / give me ideas / show me examples / getting started / what data do you have?, the onboarding entry point for an agent that just connected and wants to know what is worth asking. Returns category-bucketed example questions (company financials, drugs & clinical trials, economics, real estate, prediction markets, weather, government & patents, science & academia, news), each with the exact tool + argument shape that answers i

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": {
      "topic": "finance"
    },
    "name": "noaa-ncei__suggest_questions"
  }
}

Input Schema

NameRequiredDescriptionDefault
topicNoOptional focus area: finance | pharma | economics | real-estate | betting | weather | government | science | news. Omit for a cross-category spread.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/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 burden. It does disclose the useful behavioral detail that each returned example carries 'the exact tool + argument shape that answers' the question, which tells an agent the payload is directly actionable. However it says nothing about side effects, cost, or whether the call is a pure read, and the sentence is truncated mid-word, so the disclosure is incomplete.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description opens with nine slash-separated user phrasings that restate the same idea and push the actual purpose into the middle of the text. It then ends mid-sentence ('that answers i'), which reads as a truncation and leaves the return-value claim unfinished. Both choices hurt front-loading and signal sloppy composition.

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-parameter, no-output-schema, no-annotation discovery tool, the essentials are mostly present: what it returns, what the returned items contain, and the optional focus area. What is missing is the tail of the final sentence and any statement of the response structure (grouping, item count, ordering), which an agent would want before calling it to plan its next step.

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 optional 'topic' parameter is fully documented in the schema with its enum-like value list, so the baseline is 3. The description's parenthetical category list (financials, drugs & clinical trials, economics, real estate, prediction markets, weather, government & patents, science & academia, news) loosely parallels the topic values but does not explicitly tie them to the parameter or explain the omit-for-spread behavior that the schema already states.

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

Purpose3/5

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

The core purpose is stated in one clause — 'the onboarding entry point for an agent that just connected and wants to know what is worth asking' — and it does say it 'Returns category-bucketed example questions.' But the specific verb+resource is buried behind a slash-separated list of user phrasings ('what can you do? / give me ideas / show me examples'), so the tool's actual function (returning example questions with tool+argument shapes) has to be excavated rather than read.

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?

It clearly says when to use it: an agent that has just connected and needs to discover what is askable. That is a genuine usage condition rather than an implied one. It does not name alternatives or say when not to use it, which is acceptable here since the sibling set is the same discovery tool scoped to other datasets.

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.