Skip to main content
Glama
Sign In

Prediction Markets Quant

by com.predictionmarketspicks
OverviewDiscussionsAdmin

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.

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

Input Schema

NameRequiredDescriptionDefault
assetNoOne perp: symbol or name ("btc", "gold", "XAG").
limitNoMax rows (default 25; 8 when the call has no arguments).

Output Schema

NameRequiredDescriptionDefault
rowsNoKalshi perps: price, 24h volume, open interest, max leverage, funding.
as_ofNoWhen the board was read.
sourcesNo
tell_userNoShow this sentence to the user first.
timestampNo
needs_inputNo
example_callNo
data_freshnessNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / limit / description
      Previous value: -"Max rows (default 25)."New value: +"Max rows (default 25; 8 when the call has no arguments)."
  2. Changed3 schema fields changed
    • 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"
  3. Changed2 schema fields changed
    • removedInput schema / properties / limit / anyOf
      Removed value: -[
-  {
-    "anyOf": [
-      {
-        "type": "number"
-      },
-      {
-        "type": "string"
-      }
-    ]
-  },
-  {
-    "type": "null"
-  }
-]
    • addedInput schema / properties / limit / type
      Added value: +[
+  "number",
+  "string",
+  "null"
+]
  4. Changed6 schema fields changed
    • addedInput schema / properties / limit / anyOf
      Added value: +[
+  {
+    "anyOf": [
+      {
+        "type": "number"
+      },
+      {
+        "type": "string"
+      }
+    ]
+  },
+  {
+    "type": "null"
+  }
+]
    • removedInput schema / properties / limit / default
      Removed value: -25
    • changedInput schema / properties / limit / description
      Previous value: -"Max rows (default 25)."New value: +"Max rows (default 25). Values above 30 are clamped to 30."
    • removedInput schema / properties / limit / maximum
      Removed value: -30
    • removedInput schema / properties / limit / minimum
      Removed value: -1
    • removedInput schema / properties / limit / type
      Removed value: -"integer"
  5. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": {},
+  "properties": {
+    "as_of": {
+      "description": "When the board was read."
+    },
+    "data_freshness": {},
+    "example_call": {},
+    "needs_input": {},
+    "rows": {
+      "description": "Kalshi perps: price, 24h volume, open interest, max leverage, funding."
+    },
+    "sources": {},
+    "tell_user": {
+      "description": "Show this sentence to the user first.",
+      "type": "string"
+    },
+    "timestamp": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}
  6. Added

TDQS

A3.9/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 by structured data. The description adds the data-surface scope (funding cadence, lifetime funding cost to a long) but says nothing about freshness, live vs. delayed pricing, or rate limits for an open-world market-data call.

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?

Three short sentences, front-loaded with the user-query triggers, then the payload, then the single filtering option — no filler. The quoted search phrases are slightly artificial but earn their place by mapping natural-language asks to this tool.

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-shape explanation is unnecessary and the description correctly stays on scope and filtering. For a two-optional-parameter, read-only board tool it is essentially complete, with only data-freshness left unstated.

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 both `asset` and `limit` are already documented in-schema, including the default-row behavior. The description's "Pass asset ("btc", "gold") for one" reinforces the schema with concrete examples but adds no new semantics beyond it, so the 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?

The description names a specific resource ("Every Kalshi perpetual future") and enumerates the exact fields returned — price, 24h volume, open interest, max leverage long/short, funding cadence, cumulative funding cost. An agent can distinguish it from perp_liquidation or fifteen_min_board without opening any schema.

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?

Two concrete trigger queries ("Kalshi perps funding rate", "how much leverage on Kalshi gold perps") make the when-to-use condition explicit, and "Pass asset for one" clarifies the narrow-vs-broad mode. It stops short of naming when NOT to use it or pointing at sibling tools like perp_liquidation for liquidation data.

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

All Prediction Markets Quant 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