Skip to main content
Glama

Microverse Market Data

Kalshi perpetual futures

get_kalshi_perps
Read-onlyIdempotent

Kalshi perpetual futures: every contract with its live best bid/ask from our feed, contract size, underlying, reference and mark prices, funding cap, open interest, 24h volume and whether the market is open. asset_class filters (e.g. 'Crypto', 'Equity'). Stock perps follow stock-market hours.

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": "get_kalshi_perps"
  }
}

Input Schema

NameRequiredDescriptionDefault
open_onlyNo
asset_classNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so safety is covered. The description adds genuine behavioral context not in the annotations: prices are 'live' from the provider feed, whether a market is open is returned, and stock perps suspend outside market hours. It omits pagination/result-size behavior and what happens when no contracts match, which matters for an open-world feed.

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?

Front-loaded with the resource and the returned data, followed by two short, purposeful sentences on filtering and market hours. The long comma-separated field list is dense but each item earns its place as return-value specification.

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, the description compensates by enumerating the returned per-contract fields (bid/ask, size, underlying, reference/mark price, funding cap, OI, 24h volume, market-open flag). For a two-parameter read-only listing tool, the only material gap is pagination/ordering 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 coverage is 0%, so the description carries the burden. It explains asset_class with concrete example values, which is real added meaning, but open_only is never mentioned — the agent must infer its effect from the parameter name and the returned 'market is open' field.

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 resource (Kalshi perpetual futures contracts) and enumerates the fields returned, so an agent knows exactly what this lists versus, say, an order-book tool. It stops short of naming a sibling like get_order_book or list_symbols as the alternative for depth/symbol lookup, but the 'every contract' framing makes the broad-listing scope clear.

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?

Gives some usable context — asset_class accepts values like 'Crypto'/'Equity', and stock perps only quote during stock-market hours — which implies when results may be sparse. It never states when to choose this over get_order_book or get_consolidated_book, nor any when-not condition, so guidance is implied rather than explicit.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources