Skip to main content
Glama

NS Pros MCP Gateway

nist-fluid-properties__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": "nist-fluid-properties__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 behavioral burden. It does disclose the return shape (category buckets of example questions with tool + argument shape), which is genuinely useful, but says nothing about read-only safety, cost, latency, result size, or the fact that no arguments are needed. The final clause is truncated mid-sentence ('that answers i'), leaving the description of what each example includes incomplete.

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 leading slash-separated list of eight user phrasings is redundant with two or three and dilutes the front-loading; the real purpose statement appears only after it. The sentence describing returned categories is long, list-heavy, and cut off mid-word, so the structure is cluttered rather than economical.

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?

There is no output schema, so the description must explain returns, and it partially does by naming the category buckets and the tool + argument shape per question. However the truncation leaves the payoff undefined and there is no mention of the optional topic filter, so an agent lacks a complete picture of this low-complexity tool.

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 with its enumerated focus areas is fully documented in the schema. The description never mentions the topic parameter, so it adds no meaning beyond the schema; the 3 baseline 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 second sentence states a concrete verb and resource: returns category-bucketed example questions, each paired with the tool and argument shape that answers it. The opening slash-delimited list of user phrasings ('what can I ask Pipeworx?', 'give me ideas') is trigger-phrase bait rather than purpose, but the core statement is specific enough for an agent to distinguish this from ask_pipeworx or discover_tools.

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?

Explicitly frames the tool as 'the onboarding entry point for an agent that just connected and wants to know what is worth asking', which is a clear use condition. It implies a hand-off to the tools surfaced in the results. No when-not guidance and no named alternative (e.g. discover_tools) is given, so it stops short of 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.