Skip to main content
Glama

NS Pros MCP Gateway

nplg-catalog__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": "nplg-catalog__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?

No annotations are supplied, so the description carries the full burden. It does disclose useful internals: it resolves the market, classifies the bet, fans out evidence sources, and retries a closed-market lookup rather than failing. However, it is truncated mid-sentence ("fans ou") and says nothing about cost, latency, or what the agent receives back, leaving material behavior undisclosed.

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 opening sentence is front-loaded and efficient. The following slug-dating explanation is restated at length and duplicated in the schema, and the text ends abruptly mid-word, so the structure is neither wasteful nor complete.

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?

There is no output schema, so the description should describe what the research call yields; it begins to (resolves, classifies, fans out) but is cut off before explaining the returned evidence bundle. For a fan-out research tool spanning multiple upstream sources, that omission leaves the agent partially uninformed.

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 every parameter is already documented in the input schema, including depth enum values and the include_raw size tradeoff. The description's identifier-format and dated-slug resolution guidance substantially duplicates the market parameter's schema description, adding little beyond it. Baseline 3 applies where 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?

States a specific verb and resource: "Research a Polymarket bet by pulling the relevant Pipeworx data for it in one call," and names the accepted market identifiers. It does not differentiate itself from siblings such as polymarket_edges, polymarket_arbitrage, or deep_research, so the agent must infer which prediction-market tool to use, but the core purpose is unmistakable.

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 explains what input formats are acceptable and when to prefer a dated vs undated slug ("prefer whichever slug you actually have"), which is useful. It gives no when-to-use/when-not guidance relative to the many sibling prediction-market and research tools, so tool selection is left to inference.

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.