Skip to main content
Glama

NS Pros MCP Gateway

nsi-bg__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": "nsi-bg__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.6/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full burden. It discloses the return shape (category-bucketed example questions, each paired with the exact tool and argument shape), which is valuable given there is no output schema. However, it says nothing about whether the call is read-only, whether it costs quota or hits upstream providers, or whether output is static versus live-generated.

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 essential sentence is front-loaded enough, but it is preceded by a long slash-separated string of sample user phrases, and the final sentence is cut off mid-word. The phrasing is clearly optimized for user-utterance matching rather than agent readability, which costs structure even though most of the content is relevant.

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 one-optional-parameter, no-output-schema discovery tool, the description covers the essentials: what it is for, when to invoke it, and what comes back. Only minor gaps remain, chiefly whether it is a safe/cheap read and how exhaustive the returned category list is.

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 topic parameter's enum values are fully documented in the schema itself, so the schema does the heavy lifting. The description's enumeration of return categories (financials, drugs and clinical trials, economics, real estate, prediction markets, weather, government and patents, science, news) loosely mirrors those topics but adds no syntax, defaults, or fallback behavior for the parameter.

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 core sentence is specific: it is 'the onboarding entry point for an agent that just connected' that 'returns category-bucketed example questions' with the exact tool and argument shape that answers each. That is a clear verb+resource+scope. The noisy opening list of user utterances ("what can you do?", "give me ideas") is keyword fodder rather than a purpose statement, and the text trails off mid-sentence ("that answers i"), which slightly blurs the otherwise clear 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 names a clear usage context: use it at the start of a session when the agent has just connected and doesn't yet know what is worth asking. That is genuine when-to-use guidance beyond the name. It stops short of stating when not to use it or pointing to any alternative once the agent already knows what it wants, which is why it is not 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.