List Kalshi crypto markets (full yes/no depth, DepthFeed-exclusive). Requires a paid plan; keyless/Free returns a 402 upsell.
| Name | Required | Description | Default |
|---|---|---|---|
| coin | No | Crypto asset. Keyless/demo and Free plans are BTC-only; all 7 require a paid plan. | btc |
| type | No | Filter by market window/type. | |
| limit | No | Page size (1–100). | |
| cursor | No | Opaque pagination cursor from a previous response's pagination.next_cursor. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Beyond annotations (readOnlyHint, openWorldHint), the description adds that results are DepthFeed-exclusive and that a paid plan is required, which are important behavioral traits. No contradiction with annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences, no wasted words, and the main purpose is front-loaded. Every sentence provides value.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the presence of annotations and full schema coverage, the description is adequate but lacks details on return format or pagination behavior, which would be helpful since there is no output schema.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, and the description does not add new information about parameters beyond what is already in the schema's descriptions. The paid plan note for coin is already in the schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool lists Kalshi crypto markets with full yes/no depth, distinguishing it from other tools. However, it does not explicitly contrast with sibling tools like kalshi_get_orderbook or kalshi_get_snapshots.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides critical prerequisite information about requiring a paid plan and the 402 error for free plans. However, it offers no guidance on when to use this tool versus other Kalshi or market search tools among siblings.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool has a distinct purpose, clearly separated by venue prefix (kalshi_, limitless_, polymarket_) and action (get_orderbook, get_snapshots, search_markets). The screener and whoami tools are unique and not overlapping with any other tool.
Most tools follow the venue_verb_noun pattern (e.g., kalshi_get_orderbook, polymarket_get_snapshots). However, polymarket_all_markets uses 'all' instead of a verb, and screener/whoami deviate entirely from the pattern, causing minor inconsistency.
With 12 tools covering three venues plus cross-venue and session info, the count is well-scoped. Each tool serves a clear role without unnecessary bloat or deficiency.
The tool surface covers the core data retrieval operations (orderbook, snapshots, search, single market) for all venues. Missing are update/delete operations but those are outside the data provider scope. A minor gap is the lack of a dedicated 'get_market' for Kalshi and Limitless, though search_markets provides similar info.
