Skip to main content
Glama

AIsa Finance

by one.aisa
OverviewDiscussionsAdmin

Get Kalshi Trades

get_kalshi_trades
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.
max_tsNoFilter items before this Unix timestamp
min_tsNoFilter items after this Unix timestamp
tickerNoFilter by market ticker
is_block_tradeNoFilter trades by whether they are block trades. Omit to return all trades. Set to `true` to return only block trades. Set to `false` to return only non-block trades.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed11 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 / is_block_trade / description
      Previous value: -"Filter trades by whether they are block trades. Omit to return all trades."New value: +"Filter trades by whether they are block trades. Omit to return all trades. Set to `true` to return only block trades. Set to `false` to return only non-block trades.\n"
    • removedInput schema / properties / is_block_trade / example
      Removed value: -false
    • 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_ts / description
      Previous value: -"Filter trades before this Unix timestamp."New value: +"Filter items before this Unix timestamp"
    • changedInput schema / properties / min_ts / description
      Previous value: -"Filter trades after this Unix timestamp."New value: +"Filter items after this Unix timestamp"
    • changedInput schema / properties / ticker / description
      Previous value: -"Filter by Kalshi market ticker."New value: +"Filter by market ticker"
    • removedInput schema / properties / ticker / example
      Removed value: -"KXMVESPORTSMULTIGAMEEXTENDED-S20268A776ACB3C6-43886DEE17A"
    • addedInput schema / properties / ticker / x-go-type-skip-optional-pointer
      Added value: +true
  2. First observed

TDQS

D1.6/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is covered. The description's only real behavioral content is a per-request price ($0.02 USD), which is marginally useful cost information, but it says nothing about pagination limits, result ordering, or data freshness beyond what the schema states.

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 every sentence is injected boilerplate rather than tool documentation, and it is front-loaded with an unrelated '默认价格配置' heading. Nothing in the text earns its place for the purpose of invoking this tool.

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?

The tool has an output schema and full annotations, which lightens the burden, but the description still omits the bare essentials: that it retrieves trade history, what a trade record contains, and how filters combine. For a six-parameter market-data query, this is completely inadequate.

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 all six parameters (limit, cursor, max_ts, min_ts, ticker, is_block_trade) are already documented with defaults and constraints. The description adds no parameter meaning whatsoever; per the rubric, full schema coverage establishes a baseline of 3.

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 never states what the tool does. It consists of the phrase '默认价格配置' (default price configuration) and a pricing boilerplate block, with no verb, no resource, and no mention of Kalshi trades or markets. The only hint of purpose comes from the tool name itself, which the description does not reinforce.

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?

There is no when-to-use guidance, no exclusions, and no reference to any alternative such as get_kalshi_markets or get_polymarket_activity. The text provides zero context for selecting this tool over its ten siblings.

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