Skip to main content
Glama
Sign In
Wicked MCP server

Wicked MCP server

by WickedAPI
OverviewSchemaSourceRelated ServersDiscussions(1)Admin
TypeScript
Hybrid

kalshi_market

Read-onlyIdempotent

Fetch a single Kalshi market's orderbook depth and recent trades by ticker to assess one contract's liquidity and trading activity.

Instructions

[Trading Data API] Single Kalshi market depth: orderbook (yes/no levels) + recent trades for a specific ticker.

Example: /v1/kalshi-market?ticker=KXBTCD-26JUN1315-T64099.99

Use when you need one Kalshi market's orderbook and recent trades by ticker. Not for browsing markets by category (use kalshi_probability).

Behavior: read-only. Priced via x402 (USDC on Base) or free with WICKEDAPI_API_KEY; with neither, you get HTTP 402 with the decoded price in payment_required (a price quote, not a failure).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "ticker": "<ticker>"
    },
    "name": "kalshi_market"
  }
}

Input Schema

NameRequiredDescriptionDefault
depthNoOptional. Orderbook depth per side (default 10, max 100).
tickerYesRequired. A Kalshi market ticker (e.g. KXBTCD-26JUN1315-T64099.99).
tradesNoOptional. Recent trades to return (default 20, max 100).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.1

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly/openWorld/idempotent/non-destructive, yet the description adds genuinely new behavior: payment via x402 (USDC on Base) or WICKEDAPI_API_KEY, and that a 402 with decoded price is a quote, not a failure — a critical non-obvious detail. It stops short of describing the response shape beyond a high-level mention of orderbook/trades.

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?

Front-loads the resource and example, then usage and payment caveats in a scannable structure. Slightly padded by the markdown formatting and an example URL that duplicates the schema's ticker example, but every section carries real information.

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 3-param tool with no output schema, the definition covers what it returns at a high level (orderbook yes/no levels, recent trades), the usage boundary, and the payment-failure semantics that would otherwise confuse an agent. Full completeness would require a bit more on the returned structure, but the essentials are present.

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%, so ticker format, depth default/max, and trades default/max are already documented in the schema. The description only reinforces the ticker example already present in the schema, adding no new syntax or semantics.

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

Purpose5/5

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

States a specific verb (fetch) and resource (single Kalshi market depth: orderbook + recent trades) scoped by ticker, and explicitly names the sibling it differs from (kalshi_probability). An agent can distinguish it from the browsing tool without opening either schema.

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

Usage Guidelines5/5

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

Gives an explicit when-to-use line ("when you need one Kalshi market's orderbook and recent trades by ticker") and an explicit when-not with the alternative tool named ("Not for browsing markets by category (use kalshi_probability)"). Prerequisites are also covered via the ticker example.

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

Deploy Server

Other Tools