Skip to main content
Glama

Kalshi scanner

kalshi_scanner
Read-onlyIdempotent

Live Kalshi v2 regulated prediction-market scanner: scan open events & markets with YES/NO bid-ask probabilities, spread bps, 24h volume, open interest, and close times. $0.002 per call over x402 or X-API-Key. Not advice.

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": "kalshi_scanner"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNoOptional keyword filter.
limitNoMax markets (default 15, max 40).
paymentNosigned x402 payment payload (PAYMENT-SIGNATURE).
categoryNoOptional Kalshi category filter.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), so the bar is lower; the description still adds genuinely useful behavioral facts — a per-call cost of $0.002 and the two auth paths (x402 payment or X-API-Key). It omits pagination behavior and any rate limits, which matters for a paid scanning tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

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

A single front-loaded sentence with a colon-delimited field list; no filler and nothing buried. It is dense but readable, with the cost and disclaimer trailing rather than leading.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only scanner with four fully documented optional parameters and no output schema, the description covers what it returns and how it is paid for, which is what an agent needs before calling. Only secondary details (result ordering, behavior at empty results, auth precedence between x402 and X-API-Key) are missing.

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 every parameter (q, limit, payment, category) is already documented with defaults and bounds (default 15, max 40). The description adds no additional meaning about parameter interaction or filtering semantics, so baseline 3 applies.

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?

Uses a specific verb ('scan') plus resource ('open events & markets') and enumerates the returned fields (YES/NO bid-ask probabilities, spread bps, 24h volume, open interest, close times), which makes the scope concrete. It identifies the venue as Kalshi, which contrasts implicitly with the polymarket_scanner sibling, but never explicitly differentiates from kalshi_orderbook.

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?

Usage is implied rather than stated: an agent can infer this is the tool for surveying open Kalshi markets, but there is no explicit when-to-use/when-not guidance and no pointer to kalshi_orderbook for depth-style lookups. The payment and pricing note gives practical context but is not selection guidance.

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