Skip to main content
Glama
Sign In

GMPSignal Real-Time Intelligence MCP

by io.github.xpayrcom
OverviewDiscussionsAdmin

prediction_markets_polymarket_kalshi_scanner

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 structured items to extract.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.3/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, yet it discloses almost nothing: 'real-time' is the only trait, with no mention of auth needs, rate limits, whether results are cached or live, ordering, or what a returned item looks like. With no output schema either, an agent has no way to anticipate the response shape.

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?

It is short, but wasteful: the three platform names are listed twice in the same sentence, and the colon-plus-restatement structure adds no 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 annotations, no output schema, and no parameter detail in prose, the definition is missing everything an agent would need beyond the domain name — notably what a 'structured item' is and how the three sources differ. For a scanner-style data feed this is substantially incomplete.

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) and the schema already describes it at 100% coverage, so the schema does the work. The description adds no meaning beyond that, which is the baseline expectation when schema coverage is high.

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 names the data domain (Polymarket, Kalshi, Manifold prediction markets) but the only verb phrase is the vague 'real-time structured data extraction feed,' which restates the tool name rather than stating what is actually extracted (markets, odds, prices, volumes, resolutions?). An agent can guess the subject area but not the operation or payload.

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 guidance on when to use this tool, when not to, or what distinguishes it from the many other scanner tools in the sibling list (crypto orderbook arbitrage, DEX token scanner, DeFi yield monitor). Usage is only implied by the domain name.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All GMPSignal Real-Time Intelligence MCP toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources