Skip to main content
Glama

NS Pros MCP Gateway

ntsb-investigations__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": "ntsb-investigations__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

A3.5/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations at all, the description carries the full burden, and it does disclose the return shape (category-bucketed example questions with matching tool and argument shapes), which is genuinely useful. It says nothing about read-only behavior, cost, latency, or how many examples come back, and the final sentence is cut off mid-word, so the disclosure of the response 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.

Conciseness3/5

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

The opening string of user phrasings is front-loaded and plausibly useful for query matching, but it is a run-on with no structure and pushes the actual purpose into the second sentence. The description also ends truncated ('...that answers i'), which wastes space and suggests a copy defect.

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 single optional-parameter, read-only discovery tool with no output schema, the definition covers purpose and roughly what comes back. However, the truncated closing sentence and the absence of any note on return volume or formatting leave an agent with an incomplete picture of what it will actually receive.

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 topic field already enumerates the nine allowed focus areas and explains omitting it. The description only echoes the same category list in its return-value summary and never mentions the topic parameter, so it adds no meaning beyond the schema. 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 states a specific behavior: it returns category-bucketed example questions along with 'the exact tool + argument shape that answers' them. That distinguishes it from ordinary search tools. The long prefix of user phrasings ('what can you do?', 'give me ideas') and the truncated ending make the core purpose harder to extract, but it is still identifiable.

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 explicitly says this is 'the onboarding entry point for an agent that just connected and wants to know what is worth asking', which is clear when-to-use guidance. It does not name alternatives or when-not-to-use, but the siblings are all suggest_questions endpoints of other servers, so the practical risk of a bad tool choice is low.

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.