Skip to main content
Glama

NS Pros MCP Gateway

nlrb__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": "nlrb__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?

No annotations are supplied, so the description carries the full burden. It does disclose the return shape (category-bucketed examples with tool + argument shape) and the default scope behavior when topic is omitted, which is genuinely useful. However, it never states that the call is read-only/non-mutating, gives no sense of result count, length, or cost, and the final clause is cut off so the promised 'exact tool + argument shape' payoff is never fully delivered.

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?

Roughly the first third is a slash-delimited wall of user phrasings rather than a front-loaded statement of purpose, and the text terminates mid-word, so the most valuable sentence is incomplete. The core purpose and return-value information are present but buried and structurally disorganized.

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

Completeness4/5

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

For a simple, zero-required-parameter discovery tool with no output schema, the description covers what an agent needs: what it returns, how results are bucketed, and the optional focus parameter. The category list maps recognizably onto the same nine-odd areas named in the topic enum, so an agent can pick a topic sensibly. Only the truncation and the absent read-only confirmation keep it from being complete.

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 optional topic parameter is already documented in the schema, including the omit-for-cross-category behavior. The description adds nothing about matching between the narrative category names (e.g. 'drugs & clinical trials', 'betting') and the schema's enum values (e.g. 'pharma', 'betting'), which would have been the one place added meaning was possible. 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 names a distinct role — 'the onboarding entry point for an agent that just connected and wants to know what is worth asking' — and says it returns category-bucketed example questions with the exact tool and argument shape. That distinguishes it from ordinary data tools in the same namespace. It is undermined slightly by opening with a slash-separated list of user phrasings and by being truncated mid-sentence ('that answers i').

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 triggering condition: use this right after connecting to discover what is worth asking. It does not explicitly say when not to use it or name an alternative, but the call-precondition is unusually concrete for a discovery tool, so this goes beyond implied usage.

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.