Skip to main content
Glama

NS Pros MCP Gateway

noirlab-datalab__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": "noirlab-datalab__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?

No annotations are supplied, so the description carries the full burden. It does disclose the return content well – category-bucketed examples covering financials, drugs, economics, real estate, prediction markets, weather, government, science and news, each with the tool plus argument shape. What it omits is any statement of side effects, cost, rate limits, or that this is a pure read with no data mutation, and the final sentence is cut off mid-word.

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 purpose sentence is front-loaded and efficient, but it is preceded by a long slash-separated run of alternate user phrasings that adds bulk without much discriminating information. The description also ends abruptly mid-word ("that answers i"), which leaves the key claim about returned argument shapes incomplete.

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?

With no output schema and no annotations, the description does the necessary work: it names the categories returned and states that each entry includes the exact tool and argument shape needed to answer. That is enough for an agent to know what it will get and what to do with it. The truncation costs it the final specification of the return shape.

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 already enumerates its nine accepted values plus the omit-for-cross-category behavior. The description repeats the same category names without adding format, casing, or fallback semantics beyond the schema. Baseline 3 applies because the schema does the work.

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 identifies a specific function: an onboarding entry point that returns category-bucketed example questions, each paired with the exact tool and argument shape. The opening series of user phrasings ("what can I ask Pipeworx?", "what is Pipeworx good for?") reinforces the intent, though it reads as a keyword dump rather than a stated purpose. It is distinguishable from sibling suggest_questions tools only by the domain implied by the category list, not 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?

It states a clear triggering condition: "for an agent that just connected and wants to know what is worth asking." That tells an agent when this tool is the right first call. It does not say when to stop using it or how it relates to any non-suggestion discovery mechanism, so there is no explicit when-not guidance.

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.