Skip to main content
Glama

Kelly criterion calculator

calculate_kelly_criterion
Read-onlyIdempotent

Full and fractional Kelly risk per trade from a win rate and payoff ratio, with the edge per 1R and the break-even win rate. Computed with the same function as Clear Tape's free kelly criterion calculator page (linked in the result), not estimated. Returns the inputs, each result with its unit, the formula and the page link. Educational, not investment advice.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "winRate": "<winRate>",
      "payoff": "<payoff>",
      "fraction": "<fraction>"
    },
    "name": "calculate_kelly_criterion"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoLanguage of the returned text: "en" (default) or "zh" (Simplified Chinese).en
payoffYesPayoff ratio: average win divided by average loss (2 = winners twice the size of losers).
winRateYesWin rate in percent. Above 0, below 100.
fractionYesShare of full Kelly to use, in percent: 25 = quarter Kelly, 50 = half, 100 = full. Above 0, at most 100.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already establish readOnly, idempotent, non-destructive and closed-world behavior, so the bar is lower. The description goes beyond them by disclosing that the value is computed deterministically with the same function as the public Clear Tape page rather than estimated, that it is an educational output, and what the payload contains — meaningful context for a computation tool.

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 tight sentences that front-load what is computed, then provenance, then return contents. The closing disclaimer is the only arguably optional line, but it is short and compliance-relevant rather than filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, and the description compensates by listing the return payload (inputs, each result with its unit, the formula, the page link). Combined with the provenance note and the educational disclaimer, an agent has everything needed to call and interpret this tool.

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%, including units, ranges and the fraction semantics (25 = quarter Kelly), so the schema carries the parameter burden. The description only echoes win rate and payoff ratio as inputs without adding format or edge-case meaning, so baseline 3 is appropriate.

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 verb and resource — full/fractional Kelly risk per trade from win rate and payoff ratio — plus the derived outputs (edge per 1R, break-even win rate). The tool's identity is unambiguous among the calculate_* siblings, but the description never names a sibling or explains how it differs from calculate_position_size / calculate_expectancy beyond the concept name.

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 only implied by the purpose: an agent can infer it is for Kelly-based sizing questions, but there is no explicit when-to-use, no prerequisite statement, and no routing against the other risk calculators. The 'educational, not investment advice' line sets a scope boundary but is not an invocation guideline.

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