Skip to main content
Glama

NS Pros MCP Gateway

nvd__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": "nvd__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.7/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the full burden, and it does disclose the essential behavior: the return value is category-bucketed example questions, each paired with 'the exact tool + argument shape that answers' them. For a discovery/onboarding tool that output disclosure is the key behavioral fact. It omits whether the catalog is static, how many results come back, and the final clause is truncated mid-word ('answers i'), leaving a small gap.

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 slash-separated query phrases are front-loaded, which may help routing but is noisy and duplicates the purpose statement that follows. The substantive part ('onboarding entry point... Returns category-bucketed example questions...') is efficient and well-structured, but the text is truncated mid-sentence, which is a structural defect. Roughly a third of the content does not earn its place.

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?

With one optional parameter, no nested objects, and no output schema, this is a simple tool and the description covers its role and output shape adequately. However, without an output schema the truncated ending means the agent never learns the exact return structure, and nothing is said about result volume or whether the list is static. Complete enough to call, not complete enough to predict the response.

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?

The single optional parameter is fully documented in the schema (100% coverage) including all nine enum-like values, and the description's parenthetical category list largely repeats those same values rather than adding new meaning. Baseline 3 applies since the schema does the heavy lifting; the description's one added signal is that the cross-category default is the intended behavior when the topic is omitted.

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 names the resource and its role clearly: 'the onboarding entry point for an agent that just connected and wants to know what is worth asking,' and states it 'Returns category-bucketed example questions.' That is a specific verb+resource, so an agent knows what the tool produces. It loses a point because the first third of the text is a slash-separated list of user phrasings rather than a purpose statement, which delays the actual definition.

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 gives a clear usage context — use this when you have just connected and don't yet know what is worth asking. No explicit exclusions or alternatives are named, but given every sibling is a domain-specific variant of the same onboarding tool, the trigger condition is the useful part. An agent can decide to call this first without further inference.

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.