Skip to main content
Glama

NS Pros MCP Gateway

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

With no annotations, the description carries the burden, and it does disclose the return content: category-bucketed example questions with exact tool + argument shapes, across nine listed categories. That is genuinely useful behavior beyond structured fields since there is no output schema. However, nothing is said about cost, latency, pagination, or what happens with an unrecognized topic value.

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?

The lead-in is a slash-delimited pile of user phrasings ("what can I ask Pipeworx? / what is Pipeworx good for? / what can you do? / ..."), which delays the actual purpose statement instead of front-loading it. The description then ends mid-sentence ("...the exact tool + argument shape that answers i"), leaving an incomplete clause. The final substantive sentence earns its place; the rest is padding.

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 single optional-parameter discovery tool with no output schema, the description covers what it is for, when to reach for it, and what comes back (bucketed questions plus tool/argument shapes). The truncated ending is the only real gap; an agent has enough to call it correctly.

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 coverage is 100% and the topic parameter already documents the nine allowed values plus "Omit for a cross-category spread," so the schema does the heavy lifting. The description lists category names (company financials, drugs & clinical trials, economics, real estate, prediction markets...) that loosely map to those enum values, adding only marginal meaning. 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 states that this is "the onboarding entry point for an agent that just connected and wants to know what is worth asking" and that it "Returns category-bucketed example questions... each with the exact tool + argument shape that answers" them. That is a concrete verb (returns) and resource (example questions paired with tool/argument shapes), clearly distinct from the sibling suggest_questions tools tied to individual data domains. The opening slash-separated phrase list displaces a clean one-line purpose statement and the final sentence is truncated mid-word, which costs it the top score.

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 onboarding entry point for an agent that just connected and wants to know what is worth asking" gives an explicit usage condition and audience. It also implies a discovery/exploration context versus direct domain queries. No explicit when-not or named alternative is given, so it stops short of 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.