Skip to main content
Glama

GMPSignal Real-Time Intelligence MCP (96 Tools)

prediction_markets_polymarket_kalshi_scanner

Read-onlyIdempotent

Polymarket, Kalshi & Manifold Prediction Markets API: Real-time structured data extraction feed for Polymarket, Kalshi & Manifold Prediction Markets API.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "prediction_markets_polymarket_kalshi_scanner"
  }
}

Input Schema

NameRequiredDescriptionDefault
maxResultsNoMaximum number of records to return.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / maxResults / description
      Previous value: -"Maximum number of structured items to extract."New value: +"Maximum number of records to return."
  2. Changed1 schema field changed
    • removedInput schema / additionalProperties
      Removed value: -true
  3. Changed1 schema field changed
    • addedInput schema / additionalProperties
      Added value: +true
  4. First observed

TDQS

C2.2/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint, so the safety profile is covered. The description adds only the word 'real-time' as behavioral context, and says nothing about whether all three platforms are queried together, freshness guarantees, rate limits, pagination, or result ordering — useful facts the annotations do not supply.

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 short but circular: the platform list appears twice and the sentence loops back into itself without adding information. Brevity here reflects under-specification rather than efficient front-loading.

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 output schema, the description is the only place an agent could learn what a 'record' from this feed contains, and it does not say. For a multi-source aggregation tool (Polymarket, Kalshi, Manifold) it also fails to explain whether records are merged or tagged by source, leaving the call semantics ambiguous.

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?

There is a single optional parameter (maxResults) with 100% schema description coverage, so the baseline of 3 applies. The description adds no meaning about how maxResults interacts with the three sources (e.g. per-platform vs. combined cap), so no credit above baseline.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description restates the tool name and title almost verbatim: 'Polymarket, Kalshi & Manifold Prediction Markets API: ... feed for Polymarket, Kalshi & Manifold Prediction Markets API.' It names the data domain but never states what entity is actually returned (markets, odds, prices, resolutions) or what the tool does to them beyond the vague phrase 'structured data extraction feed'.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no prerequisites, and no mention of when another tool should be preferred. The many sibling scanner tools imply an agent must already know this one's niche; the description does nothing to route it.

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.

Resources