Skip to main content
Glama

NS Pros MCP Gateway

npi-registry__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": "npi-registry__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 supplied, the description must carry the full behavioral burden. It does disclose the return shape (bucketed example questions, each paired with a tool and argument template) and implicitly a read-only, non-destructive nature. However, the text is truncated mid-sentence ('that answers i'), leaving the output contract partially unstated, and no mention of volume/size of the response.

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 real description is one informative sentence, but it is preceded by a slash-separated block of quoted user intents ('what can I ask Pipeworx?', 'give me ideas', etc.) that reads as query samples rather than definitional content. The trailing sentence is cut off mid-word, which harms structure and wastes the strongest explanatory slot.

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 zero-required-parameter discovery tool with no output schema, the description supplies the essential picture: what it returns and why to call it. Gaps remain: the truncated ending, no indication of response size, and a brand name ('Pipeworx') that does not match the npi-registry namespace, which could confuse an agent about scope.

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%, so the schema already documents the single optional `topic` parameter, establishing a baseline of 3. The description's category list (company financials, drugs & clinical trials, prediction markets, etc.) loosely parallels the enum values but uses different labels ('betting' vs 'prediction markets', 'pharma' vs 'drugs & clinical trials'), adding little and risking a mapping mismatch.

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 gives a specific verb+resource: it returns category-bucketed example questions with the exact tool plus argument shape that answers them, and names its role as an 'onboarding entry point'. A reader knows exactly what comes back. It does not explicitly contrast itself with sibling suggest_questions tools, relying on the namespace for that differentiation.

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 states the triggering situation: 'an agent that just connected and wants to know what is worth asking', which is a usable when-to-use condition. It stops short of stating when NOT to call it (e.g., once the agent already knows its target tool) or naming any alternative discovery mechanism.

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.