Skip to main content
Glama

NS Pros MCP Gateway

nvd__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": "nvd__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, the description must carry the full behavioral burden. It does disclose useful traits beyond a bare lookup: dated slugs still resolve after settlement, the resolver retries a closed-market lookup, and the call fans out across sources. However, the description is truncated mid-word ("fans ou"), so the most important behavioral detail, what the fan-out actually produces and costs, is 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.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The definition is front-loaded with a clear purpose sentence, but it ends abruptly mid-word, which is a structural defect an agent may read as incomplete guidance. The mid-section spends several clauses on dated-slug resolution semantics that repeat the market parameter description, diluting the useful content.

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?

For a multi-source research tool with no output schema and no annotations, the agent needs to know what comes back and roughly what it costs. The description covers input formats and the include_raw output-size tradeoff, but the truncated fan-out sentence leaves the response shape and scope unexplained, so an agent cannot fully anticipate the result.

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 in the schema, including the depth enum and the include_raw size tradeoff. The description's only added parameter information is the slug-format hint, which largely duplicates the market field description. Baseline 3 applies when the schema does the heavy lifting.

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?

Opens with a specific verb and resource: "Research a Polymarket bet by pulling the relevant Pipeworx data for it in one call." That distinguishes it from a generic lookup and tells the agent this is a one-shot aggregation. It does not explain how it differs from the many sibling *__bet_research tools beyond the implied data source, but the core purpose is unambiguous.

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?

Gives concrete input guidance (slug, polymarket.com URL, or question text) and a selection rule for dated vs undated slugs ("prefer whichever slug you actually have"). It never states when to choose this tool over alternatives or what inputs are inappropriate, and the sentence explaining the fan-out behavior is cut off, so the usage context is only partially delivered.

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.