Crawlora MCP

Official

by Crawlora-org

Overview Schema Source Related Servers Discussions Admin

JavaScript

Remote

kalshi_exchange_schedule

Retrieve Kalshi exchange trading hours and maintenance windows to check when markets are open or closed.

Instructions

Kalshi exchange schedule. Returns the Kalshi exchange schedule, with no inputs. standard_hours are date-bounded blocks listing open_time and close_time for each weekday, and maintenance_windows list start time, end time and reason. The maintenance list can be empty. Informational only.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "kalshi_exchange_schedule"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.1.0Jun 12, 2026

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 the return structure: standard_hours as date-bounded blocks of open_time/close_time per weekday, maintenance_windows with start, end and reason, and that the maintenance list may be empty. It omits auth/rate-limit context, but for a no-input informational read the payload disclosure is the key behavioral fact.

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?

Purpose is front-loaded, followed by payload details, with no filler. The opening 'Kalshi exchange schedule.' mildly restates the name before the fuller 'Returns the Kalshi exchange schedule' sentence, a small redundancy.

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 must cover return values, and it does describe the two documented structures and the empty-maintenance case. It could say more about top-level response shape or date formats, but it is sufficient to call the tool correctly.

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?

The tool takes zero parameters, which is the baseline-4 case. The description reinforces this by explicitly saying 'with no inputs,' so an agent will not look for arguments.

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 ('Returns') and resource ('Kalshi exchange schedule') and enumerates the payload contents. It does not explicitly distinguish itself from the sibling kalshi_exchange_status, so it stops short of a 5, but the resource is unambiguous.

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: 'with no inputs' and 'Informational only' hint that this is a read-only lookup needing no arguments, but there is no explicit when-to-use or when-not, and no alternative tool is named despite a closely related kalshi_exchange_status sibling.

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

Deploy Server