Skip to main content
Glama
SakethSripada

KalTrader MCP

kalshi_create_order_v2

Submit event-market orders via the V2 endpoint, using single-book bid/ask side and fixed-point dollar prices. Migrate from the legacy /portfolio/orders endpoint to this path.

Instructions

Create Order (V2) Endpoint for submitting event-market orders using the V2 request/response shape (single-book bid/ask side and fixed-point dollar prices). The legacy /portfolio/orders endpoint will be deprecated no earlier than May 6, 2026 — clients should migrate to this path. Calls POST /portfolio/events/orders.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sideYes
countYesString representation of the order quantity in contracts.
priceYesPrice for the order in fixed-point dollars.
tickerYes
post_onlyNo
subaccountNoThe subaccount number to use for this order. 0 is the primary subaccount. Subaccount-restricted API keys must omit this field or pass their locked subaccount.
reduce_onlyNoSpecifies whether the order place count should be capped by the member's current position.
time_in_forceYesSpecifies how long the order remains active. Use `good_till_canceled` with `expiration_time` for an order that should rest until a specific expiration time; without `expiration_time`, `good_till_canceled` is a true good-till-canceled order. `GTT` is not a valid API value.
exchange_indexNoExchange shard index. Defaults to 0. Use -1 to auto-route by market ticker.
order_group_idNoThe order group this order is part of
client_order_idNo
expiration_timeNoOptional Unix timestamp in seconds for when the order expires. To place an expiring order, set `time_in_force` to `good_till_canceled` and provide this `expiration_time`. `GTT` is an internal execution type and is not a valid API value for `time_in_force`. The `immediate_or_cancel` time-in-force value cannot be combined with `expiration_time`.
cancel_order_on_pauseNoIf this flag is set to true, the order will be canceled if the order is open and trading on the exchange is paused for any reason.
self_trade_prevention_typeYes
Behavior3/5

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

The description discloses the HTTP method and endpoint path and notes the future deprecation, but it does not cover authentication requirements, live trading implications, or error behavior. Annotations only provide basic read/write hints, so the description adds some context but not enough for a live-order tool.

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

Conciseness5/5

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

Three concise sentences deliver purpose, migration guidance, and endpoint info without redundancy. Every sentence contributes a distinct, useful piece of information.

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?

The tool is complex (14 parameters, no output schema), yet the description omits what response to expect, preconditions like API credentials or available funds, and typical failure modes. It covers the endpoint and migration but leaves gaps for a live order submission tool.

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?

The description does not explain any parameters, but the input schema already provides detailed descriptions for most fields (e.g., `side`, `count`, `price`, `time_in_force`, `self_trade_prevention_type`). With ~64% schema coverage, the schema carries the parameter burden, and the description adds no extra meaning.

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?

The description clearly states it creates event-market orders using the V2 request/response shape, identifies the specific endpoint path, and distinguishes itself from the legacy endpoint via deprecation guidance. This differentiates it from sibling tools like kalshi_batch_create_orders_v2.

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

Usage Guidelines4/5

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

It explicitly advises migration from the legacy `/portfolio/orders` endpoint, providing a clear directive on when to use this tool. However, it does not mention alternatives such as `kalshi_batch_create_orders_v2` for multiple orders or `kalshi_paper_order` for testing, so exclusions are incomplete.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/SakethSripada/KalTraderMCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server