Skip to main content
Glama

AIsa Finance

by one.aisa
OverviewDiscussionsAdmin

Get Kalshi Markets

get_kalshi_markets
Read-onlyIdempotent

默认价格配置

Published reference price: $0.02 USD per successful request. Account-specific pricing and final settlement may differ.

Input Schema

NameRequiredDescriptionDefault
limitNoNumber of results per page. Defaults to 100. Maximum value is 1000.
cursorNoPagination cursor. Use the cursor value returned from the previous response to get the next page of results. Leave empty for the first page.
statusNoFilter by market status. Leave empty to return markets with any status.
tickersNoFilter by specific market tickers. Comma-separated list of market tickers to retrieve.
mve_filterNoFilter by multivariate events (combos). 'only' returns only multivariate events, 'exclude' excludes multivariate events.
event_tickerNoEvent ticker to filter by. Only a single event ticker is supported.
max_close_tsNoFilter items that close before this Unix timestamp
min_close_tsNoFilter items that close after this Unix timestamp
series_tickerNoFilter by series ticker
max_created_tsNoFilter items that created before this Unix timestamp
max_settled_tsNoFilter items that settled before this Unix timestamp
max_updated_tsNoReturn markets with metadata updated at or before this Unix timestamp (in seconds). Tracks non-trading changes only. May be combined with min_updated_ts and mve_filter=exclude. May also be combined with series_ticker, which requires mve_filter=exclude. Incompatible with other filters.
min_created_tsNoFilter items that created after this Unix timestamp
min_settled_tsNoFilter items that settled after this Unix timestamp
min_updated_tsNoReturn markets with metadata updated later than this Unix timestamp (in seconds). Tracks non-trading changes only. May be combined with max_updated_ts and mve_filter=exclude. May also be combined with series_ticker, which requires mve_filter=exclude. Incompatible with other filters.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed23 schema fields changed
    • changedInput schema / properties / cursor / description
      Previous value: -"Pagination cursor from the previous response."New value: +"Pagination cursor. Use the cursor value returned from the previous response to get the next page of results. Leave empty for the first page."
    • addedInput schema / properties / cursor / x-go-type-skip-optional-pointer
      Added value: +true
    • changedInput schema / properties / event_ticker / description
      Previous value: -"Filter by a single Kalshi event ticker."New value: +"Event ticker to filter by. Only a single event ticker is supported."
    • removedInput schema / properties / event_ticker / example
      Removed value: -"KXMVESPORTSMULTIGAMEEXTENDED-S20268A776ACB3C6"
    • addedInput schema / properties / event_ticker / x-go-type-skip-optional-pointer
      Added value: +true
    • removedInput schema / properties / limit / example
      Removed value: -100
    • addedInput schema / properties / limit / x-oapi-codegen-extra-tags
      Added value: +{
+  "validate": "omitempty,gte=0,lte=1000"
+}
    • changedInput schema / properties / max_close_ts / description
      Previous value: -"Filter markets closing before this Unix timestamp."New value: +"Filter items that close before this Unix timestamp"
    • changedInput schema / properties / max_created_ts / description
      Previous value: -"Filter markets created before this Unix timestamp."New value: +"Filter items that created before this Unix timestamp"
    • changedInput schema / properties / max_settled_ts / description
      Previous value: -"Filter markets settled before this Unix timestamp."New value: +"Filter items that settled before this Unix timestamp"
    • addedInput schema / properties / max_updated_ts
      Added value: +{
+  "description": "Return markets with metadata updated at or before this Unix timestamp (in seconds). Tracks non-trading changes only. May be combined with min_updated_ts and mve_filter=exclude. May also be combined with series_ticker, which requires mve_filter=exclude. Incompatible with other filters.",
+  "format": "int64",
+  "type": "integer"
+}
    • changedInput schema / properties / min_close_ts / description
      Previous value: -"Filter markets closing after this Unix timestamp."New value: +"Filter items that close after this Unix timestamp"
    • changedInput schema / properties / min_created_ts / description
      Previous value: -"Filter markets created after this Unix timestamp."New value: +"Filter items that created after this Unix timestamp"
    • changedInput schema / properties / min_settled_ts / description
      Previous value: -"Filter markets settled after this Unix timestamp."New value: +"Filter items that settled after this Unix timestamp"
    • changedInput schema / properties / min_updated_ts / description
      Previous value: -"Filter markets updated after this Unix timestamp."New value: +"Return markets with metadata updated later than this Unix timestamp (in seconds). Tracks non-trading changes only. May be combined with max_updated_ts and mve_filter=exclude. May also be combined with series_ticker, which requires mve_filter=exclude. Incompatible with other filters."
    • changedInput schema / properties / mve_filter / description
      Previous value: -"Filter by multivariate events."New value: +"Filter by multivariate events (combos). 'only' returns only multivariate events, 'exclude' excludes multivariate events."
    • removedInput schema / properties / search
      Removed value: -{
-  "description": "Search markets by keywords in title and description. Must be URL encoded (e.g., 'bitcoin%20price' for 'bitcoin price').",
-  "example": "bitcoin",
-  "type": "string"
-}
    • changedInput schema / properties / series_ticker / description
      Previous value: -"Filter by series ticker."New value: +"Filter by series ticker"
    • addedInput schema / properties / series_ticker / x-go-type-skip-optional-pointer
      Added value: +true
    • changedInput schema / properties / status / description
      Previous value: -"Filter markets by status."New value: +"Filter by market status. Leave empty to return markets with any status."
    • removedInput schema / properties / status / example
      Removed value: -"open"
    • changedInput schema / properties / tickers / description
      Previous value: -"Comma-separated Kalshi market tickers to retrieve."New value: +"Filter by specific market tickers. Comma-separated list of market tickers to retrieve."
    • removedInput schema / properties / tickers / example
      Removed value: -"KXMVESPORTSMULTIGAMEEXTENDED-S20268A776ACB3C6-43886DEE17A"
  2. First observed

TDQS

D1.4/5.0
Behavior1/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world behavior. The description adds nothing about pagination limits, result ordering, or rate/price behavior beyond a static price snippet – the one relevant line (per-request cost) is vague and unrelated to tool mechanics.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short, but it is also front-loaded with irrelevant pricing markup rather than purpose. Conciseness without substance is under-specification, not quality.

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

Completeness1/5

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

For a 15-parameter read tool with siblings like get_polymarket_markets, an output schema present, and rich filtering semantics, the description supplies zero functional context. An agent has nothing to decide selection or interpretation beyond the schema.

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%, and each parameter (limit, cursor, status, tickers, timestamps) is well-documented in the schema. The description adds no parameter meaning, so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description contains only pricing boilerplate ('默认价格配置' / published reference price) and says nothing about what the tool does. An agent cannot tell from this text that it retrieves Kalshi markets or how it differs from get_polymarket_markets or get_kalshi_trades.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

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

No when-to-use guidance, no exclusions, and no reference to sibling tools. The pricing note provides no invocation guidance whatsoever.

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

All AIsa Finance toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources