Skip to main content
Glama

NS Pros MCP Gateway

noaa-ncei__bet_research

Research a Polymarket bet by pulling the relevant Pipeworx data for it in one call. Pass a market slug ("will-kristi-noem-win-the-2028-republican-presidential-nomination"), a polymarket.com URL, or a question text. A dated slug ("...-by-june-30-2026") still resolves after it settles, the resolver retries a closed-market lookup rather than giving up on the bare one, so either dated or undated works; prefer whichever slug you actually have. The tool resolves the market, classifies the bet, fans ou

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": {
      "market": "will-kristi-noem-win-the-2028-republican-presidential-nomination"
    },
    "name": "noaa-ncei__bet_research"
  }
}

Input Schema

NameRequiredDescriptionDefault
depthNoquick = 2-3 evidence sources, thorough = full fan-out. Default thorough.
marketYesPolymarket slug ("will-kristi-noem-win-the-2028-republican-presidential-nomination"), full URL ("https://polymarket.com/event/..."), or question text ("Will Bitcoin hit $150k?"). Dated slugs still resolve after they settle, the resolver retries a closed-market lookup, so either a dated or undated slug works.
include_rawNoDefault false. When false (recommended), FRED/FDA/GDELT/Federal-Register evidence is summarized to the few fields agents actually use, keeps responses under ~20KB. Pass true to get full upstream payloads (50KB-500KB) when you need to recompute deltas, cite specific observations, or post-process.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/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 usefully discloses resolver behavior (retries a closed-market lookup for dated slugs that have settled) and response-size economics (summary under ~20KB vs. 50KB–500KB raw payloads). It does not state whether the call is read-only, how long fan-out takes, whether results are cached, or what the response contains — and the text is cut off mid-clause ('fans ou') exactly where the output behavior would have been described.

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 slug guidance is front-loaded and the sentence about dated slugs resolving after settlement earns its place. However, it duplicates schema text, and the definition terminates mid-word ('fans ou'), leaving the most consequential sentence — what the tool actually returns — unfinished.

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

Completeness2/5

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

With no annotations and no output schema, and a fan-out/classification tool that aggregates multiple upstream sources, the description should explain the returned artifact (classification, evidence set, verdict?) and the cost/latency of the thorough path. The truncated final sentence removes precisely that information, so an agent cannot predict the response shape before calling.

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%, so all three parameters are already documented, including the depth enum and the include_raw size trade-off. The description's slug sentence largely restates the market parameter's schema text verbatim, so it adds little meaning beyond structured fields. 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 opening sentence gives a specific verb and resource: 'Research a Polymarket bet by pulling the relevant Pipeworx data for it in one call.' That is clearly distinct from a generic research tool. It stops short of differentiating this instance from the many sibling provider-specific bet_research tools (noaa-coastwatch, neiss, nhtsa, etc.), so an agent cannot tell from the text why it would pick the NCEI variant.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives clear input-shape guidance (slug, URL, or question text) and a preference rule ('prefer whichever slug you actually have'), plus a depth trade-off implied by the schema. It gives no guidance on when to choose this over sibling tools like deep_research or research_row, and no prerequisites or exclusions.

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.