Skip to main content
Glama

NS Pros MCP Gateway

nj-mvc__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": "nj-mvc__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.4/5.0
Behavior3/5

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

With no annotations, the description carries full behavioral burden; it does disclose the return shape as category-bucketed example questions paired with 'the exact tool + argument shape', which is meaningful beyond structured fields. However, that sentence is truncated mid-word ('answers i'), so the account of what each result contains is incomplete, and nothing is said about read-only side effects or result size.

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 slash-separated trigger phrasings are useful for intent matching but consume roughly half the text before the actual purpose is stated, so it is not front-loaded. The definition also ends abruptly mid-sentence, which is a real structural defect rather than mere brevity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with no output schema, the description is responsible for explaining return values, and it cuts off exactly where that explanation begins ('the exact tool + argument shape that answers i'). An agent gets the gist but not the full response contract, and there is no annotation coverage to fill the gap.

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% and the single 'topic' parameter already documents its allowed values and the omit-for-all behavior, so the schema does the heavy lifting. The description's category list ('company financials, drugs & clinical trials, economics, real estate...') roughly parallels the schema enum but uses different labels, adding little new semantics.

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 a specific resource ('category-bucketed example questions') and frames the tool as 'the onboarding entry point for an agent that just connected', which is a clear verb-and-resource statement. It also implicitly distinguishes itself from data-query siblings by being the discovery layer, though it never names an alternative tool explicitly.

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?

The leading list of user phrasings ('what can I ask Pipeworx?', 'give me ideas', 'getting started') gives concrete triggers for invocation, and 'the onboarding entry point for an agent that just connected' states the situation clearly. No when-not-to-use or exclusions are offered, which keeps it below a 5.

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.