Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

kalshi_series

List Kalshi series with ticker, title, category, frequency, fees, settlement sources, and contract URLs; set limit up to 200.

Instructions

Kalshi series. Lists Kalshi series, up to limit rows (default 25, max 200). Each series has its ticker, title, category, frequency, fee type and multiplier, settlement sources, and contract and contract-terms URLs. The catalogue comes back in one page, so cursor has no effect on this endpoint.

Input Schema

NameRequiredDescriptionDefault
limitNoRows to return, default 25, max 200
cursorNoPagination cursor from a previous Kalshi response

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.6.0
  2. Removedv1.6.0
  3. Addedv1.1.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose non-obvious behavior: the catalogue returns in a single page and cursor is ineffective. It also enumerates return fields. It stops short of stating read-only semantics or auth/rate-limit behavior.

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?

Three tight sentences, front-loaded with the core purpose, then the return shape, then the pagination caveat. No filler, though the field enumeration is slightly listy.

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?

No output schema exists, so the description correctly compensates by naming the returned fields (ticker, title, category, frequency, fee type, URLs). It covers pagination behavior; the main gap is the absence of any read-only/authorization statement, which would be needed given no annotations.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3, but the description adds meaning beyond the schema by clarifying that the cursor parameter has no effect on this endpoint and restating limit's default/max in context. This is a genuine semantic addition over the schema text.

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?

States a specific verb and resource ('Lists Kalshi series') and enumerates the fields returned, so the agent knows exactly what comes back. It does not explicitly distinguish itself from the sibling kalshi_series_detail, so it falls short of a 5.

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 only implied by 'Lists Kalshi series' and the pagination note; there is no explicit when-to-use or when-to-prefer-an-alternative guidance (e.g., kalshi_series_detail for a single series). The 'cursor has no effect' note is a useful operational hint but not a usage rule.

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