Skip to main content
Glama

NS Pros MCP Gateway

nsi-bg__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": "nsi-bg__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.3/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 disclosure burden. It does add genuine behavior context beyond the schema: the resolver retries a closed-market lookup so settled dated slugs still resolve, and the tool 'resolves the market, classifies the bet, fans ou[t]'. But the sentence is cut off, so the fan-out and return behavior are never fully disclosed, and nothing is said about read-only semantics, latency, or cost of a thorough run.

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 purpose is front-loaded and the slug guidance is practical, but the dated-slug explanation is discursive and restates itself ('the resolver retries a closed-market lookup rather than giving up on the bare one, so either dated or undated works'). The text also terminates mid-word ('fans ou'), leaving the most informative clause unfinished.

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?

No output schema exists, so the description must convey what comes back, and it only gestures at it ('classifies the bet, fans ou[t]') before truncating. For a three-parameter, multi-source research tool with zero annotations, the input forms are well covered but the result shape and cost profile are not.

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 baseline is 3; depth and include_raw are fully documented in the schema and need no restatement. The description reinforces the market parameter's accepted forms and adds the dated-slug resolution nuance, a marginal gain over 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?

States a specific verb+resource: 'Research a Polymarket bet by pulling the relevant Pipeworx data for it in one call.' An agent can tell this is a one-shot market research tool. It does not, however, distinguish itself from siblings such as polymarket_edges, polymarket_edge_tracker, or deep_research, so the boundary is left implicit.

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?

It gives concrete input guidance (slug, polymarket.com URL, or question text) and a resolution rule for dated vs undated slugs, including a stated preference ('prefer whichever slug you actually have'). It never states when to choose this over the sibling polymarket research tools, nor any exclusions or prerequisites.

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.