Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

kalshi_multivariate_events

Lists Kalshi multivariate events that regular event lists omit, including ticker, series, title, category, and markets. Supports limit and cursor pagination.

Instructions

Kalshi multivariate events. Lists Kalshi multivariate events, which the regular events list leaves out, up to limit rows (default 25, max 200), continued with cursor. Each event has its ticker, series ticker, title, subtitle, category and markets. A cursor is returned when more rows exist.

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

A4.2/5.0
Behavior4/5

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

With no annotations provided, the description carries the full behavioral burden and does reasonably well: it discloses pagination semantics (default 25, max 200), that a cursor is returned only when more rows exist, and what fields each returned event contains. It doesn't state authorization or rate-limit behavior, but for a read-only list endpoint this is solid.

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 sentences, zero waste, and front-loaded with the resource before the scoping constraint and pagination details. Nothing redundant or padded.

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?

With no output schema and only two optional params, the description supplies everything needed: pagination behavior, the fields returned per event, and the scoping contrast with kalshi_events. Adequate for correct invocation, though it omits any indication of ordering or empty-result behavior.

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 description coverage is 100%, so both limit and cursor are already documented in the schema. The description restates their defaults/bounds and adds only that the cursor comes from a prior Kalshi response, providing minimal value beyond the schema. Baseline 3 is appropriate.

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 (Lists) and resource (Kalshi multivariate events) and explicitly differentiates from the sibling kalshi_events by noting these are 'events which the regular events list leaves out.' An agent can tell exactly which tool to pick 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 Guidelines4/5

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

The phrase 'which the regular events list leaves out' implies when to use this over kalshi_events, giving clear routing context. However, it stops short of an explicit when-to-use/when-not-to-use statement or naming the alternative tool directly.

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