DegenHedge: Kalshi Bitcoin 15-minute data

Kalshi fee and breakeven

kalshi_fee

Read-onlyIdempotent

Kalshi's taker fee for an order on a Kalshi contract (selected balance precision; same single-fill estimate as https://degenhedge.com/tools/kalshi-fee-calculator/), the total cost, profit if it wins, loss if it loses and the win rate needed to break even. price_cents is in CENTS (95 = a 95-cent contract). KXBTC15M charges makers no fee.

Input Schema

Name	Required	Description	Default
`maker`	No	true for a resting (maker) order
`contracts`	No	Number of contracts
`price_cents`	Yes	Contract price in cents, 0.1 to 99.9 (whole cents between 10 and 90)
`balance_precision`	No	Dollars: 0.01 non-direct member, 0.0001 direct member	0.01

Output Schema

Name	Required	Description
`input`	Yes
`notes`	No
`matches`	No
`fee_rule`	No
`fee_cents`	Yes	Model fee plus balance rounding, in cents; may be fractional.
`disclaimer`	Yes
`fee_schedule`	Yes
`total_cost_cents`	Yes
`entry_price_bucket`	No
`loss_if_lose_cents`	No
`profit_if_win_cents`	No
`record_at_this_price`	No
`wins_needed_per_loss`	No	null when the fee takes the whole profit
`breakeven_win_rate_pct`	Yes	Win rate needed to break even after the fee
`fee_per_contract_cents`	No
`breakeven_before_fees_pct`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedOct 16, 2026

addedInput schema / properties / balance_precision

Added value: +{
+  "default": "0.01",
+  "description": "Dollars: 0.01 non-direct member, 0.0001 direct member",
+  "enum": [
+    "0.01",
+    "0.0001"
+  ],
+  "type": "string"
+}

changedOutput schema / properties / fee_cents / description

Previous value: -"Total order fee in whole cents"New value: +"Model fee plus balance rounding, in cents; may be fractional."

changedOutput schema / properties / fee_cents / type
```
Previous value: -"integer"New value: +"number"
```

addedOutput schema / properties / input / properties / balance_precision_dollars

Added value: +{
+  "enum": [
+    "0.01",
+    "0.0001"
+  ],
+  "type": "string"
+}

First observedOct 9, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description is consistent with a pure calculator. It adds real behavioral context the annotations cannot: this is a single-fill estimate, it mirrors the degenhedge calculator, and KXBTC15M charges makers no fee. It stops short of noting rounding or multi-fill caveats.

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 core purpose and outputs followed by unit clarification and the maker exception. Slightly cluttered by the parenthetical calculator reference and URL, which add provenance but little operational value.

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?

An output schema exists, so return values need not be explained, yet the description still summarizes them helpfully. Combined with the unit convention and precision option, an agent has enough to call it correctly; only edge-case behavior (rounding, multi-fill) is unaddressed.

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 four parameters are already documented, including the maker flag and balance_precision enum. The description restates the cents unit convention (95 = a 95-cent contract) and the maker-fee exception, which is marginally additive but largely duplicates the schema.

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 precise computation (Kalshi taker fee for an order) and enumerates the exact outputs: total cost, profit if it wins, loss if it loses, and breakeven win rate. An agent can tell instantly what this tool returns; the sibling tools (get_btc_window, get_graded_record) are unrelated, so no differentiation is required.

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?

Usage is implied by the wording — calculate fee/breakeven for an order — but there is no explicit when-to-use or when-not statement and no named alternative. The note that KXBTC15M charges makers no fee is useful situational context, but it does not tell the agent when to reach for this tool versus another.

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

All DegenHedge: Kalshi Bitcoin 15-minute data 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.

Resources

Need Help?