Crypto Markets Desk

Kalshi Perps Board — price, leverage and funding for every perp

perps_board

Read-only

Use for "Kalshi perps funding rate" and "how much leverage on Kalshi gold perps". Every Kalshi perpetual future: price, 24h volume, open interest, max leverage long and short, funding cadence, and what funding has cost a long since launch. Pass asset ("btc", "gold") for one.

Input Schema

Name	Required	Description	Default
`asset`	No	One perp: symbol or name ("btc", "gold", "XAG").
`limit`	No	Max rows (default 25).

Output Schema

Name	Required	Description
`rows`	No	Kalshi perps: price, 24h volume, open interest, max leverage, funding.
`as_of`	No	When the board was read.
`sources`	No
`tell_user`	No	Show this sentence to the user first.
`timestamp`	No
`needs_input`	No
`example_call`	No
`data_freshness`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 23, 2026

removedInput schema / $schema

Removed value: -"https://json-schema.org/draft/2020-12/schema"

changedInput schema / properties / limit / description

Previous value: -"Max rows (default 25). Values above 30 are clamped to 30."New value: +"Max rows (default 25)."

removedOutput schema / $schema

Removed value: -"https://json-schema.org/draft/2020-12/schema"

Changed2 schema fields changedOct 15, 2026

removedInput schema / properties / limit / anyOf

Removed value: -[
-  {
-    "anyOf": [
-      {
-        "type": "number"
-      },
-      {
-        "type": "string"
-      }
-    ]
-  },
-  {
-    "type": "null"
-  }
-]

addedInput schema / properties / limit / type

Added value: +[
+  "number",
+  "string",
+  "null"
+]

First observedOct 10, 2026

TDQS

A4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds that it aggregates derived metrics (funding cost since launch) but says nothing about data freshness, rate limits, pagination, or what happens when asset doesn't match — modest added context beyond annotations.

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 short sentences, front-loaded with the search phrasings an agent would map to this tool, then the payload contents, then the narrowing parameter. No filler.

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 an output schema present, return values needn't be spelled out, yet the description still summarizes the payload well. Minor gaps around freshness and interaction with limit/pagination keep it from a 5, but an agent has everything needed to invoke it correctly.

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 100% and the schema already names both parameters with examples ("btc", "gold", "XAG") and a default of 25. The description's "Pass asset (\"btc\", \"gold\") for one" restates what the schema documents, so baseline 3 applies.

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 resource (every Kalshi perpetual future) and enumerates exactly what it returns — price, 24h volume, open interest, max leverage long/short, funding cadence, cumulative funding cost to a long. An agent can immediately tell this is a board/screener rather than a single-perp query like perp_liquidation.

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?

Opens with two concrete example queries ("Kalshi perps funding rate", "how much leverage on Kalshi gold perps") that anchor when to reach for it, and says passing asset narrows to one entry. It stops short of naming a sibling alternative or an explicit when-not condition, so it lands just under the top band.

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

All Crypto Markets Desk tools Inspect

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.