Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

kalshi_series_detail

Fetch Kalshi series details by ticker, including title, category, frequency, fees, settlement sources, and contract URLs; unknown tickers return a not-found error.

Instructions

Kalshi series detail. Returns one Kalshi series by series_ticker (such as KXELONMARS). The response has the title, category, frequency, fee type and multiplier, settlement sources with name and URL, contract and contract-terms URLs, and last update time. An unknown ticker returns a not-found error.

Input Schema

NameRequiredDescriptionDefault
series_tickerYesKalshi series ticker

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

A4.3/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 so well: it declares this is a read that returns one series, enumerates the returned fields, and explicitly discloses error behavior ('An unknown ticker returns a not-found error'). It stops short of stating auth or rate-limit characteristics, but for a read-only lookup that is a minor omission.

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?

Purpose is front-loaded, followed by return contents and then the error case, in three tight sentences. The dense field enumeration earns its place because no output schema exists to carry that information.

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

Completeness5/5

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

For a single-parameter read tool with no annotations and no output schema, the description covers everything an agent needs: what it is, the required identifier with an example, the shape of the response, and the failure mode. Nothing material is missing.

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 the baseline is 3, and the description clears that bar by adding a concrete example ticker (`KXELONMARS`) that conveys the expected format beyond the schema's terse 'Kalshi series ticker'. It adds format guidance even though it adds no other constraint information.

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 states a specific verb and resource — 'Returns one Kalshi series by `series_ticker`' — and the singular 'one ... by ticker' framing distinguishes it from a listing sibling like kalshi_series. It even supplies a concrete ticker example (`KXELONMARS`), so an agent knows exactly what this retrieves without opening the schema.

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: the agent should call it when it has a known series ticker and wants that series' details. However, the description never names an alternative (e.g. kalshi_series for listing, kalshi_event for events) or states when NOT to use it, so there is no explicit routing guidance.

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