Skip to main content
Glama

NS Pros MCP Gateway

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

With no annotations supplied, the description carries the full burden. It does disclose real behavior: single-call fan-out, market resolution, bet classification, and that the resolver retries a closed-market lookup instead of failing on the bare slug. However, the text is cut off mid-sentence ('fans ou'), so the fan-out outcome, cost/latency, and error behavior are never delivered.

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 front-loaded first sentence is efficient, but the dated-slug explanation is repeated at length and duplicated almost verbatim in the market parameter's schema description. The text also terminates mid-word, which hurts structure and leaves the reader without the promised fan-out detail.

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?

For a tool with no annotations and no output schema, the description must cover what comes back and what 'fan-out' produces, and it is truncated exactly where that explanation begins. An agent knows how to call it but not what to expect in the response or how costly a 'thorough' run 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%, so the schema already documents all three parameters in detail, making 3 the baseline. The description echoes the market input forms and the dated-slug resolution rule but adds nothing about the depth or include_raw parameters, which are covered only by the schema.

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 opens with a specific verb and resource ('Research a Polymarket bet') and adds the mechanism ('pulling the relevant Pipeworx data for it in one call'), which tells an agent this is a one-shot aggregator rather than a raw data lookup. It does not explicitly name which sibling to prefer (e.g., deep_research or polymarket_edges), so the differentiation is implied rather than stated.

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?

Guidance is focused on input forms ('slug, URL, or question text') and the dated-vs-undated slug rule, which is genuinely useful for invocation. There is no statement of when to choose this over alternatives like deep_research or polymarket_edges, and no exclusions, so usage context is only implied.

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.