Skip to main content
Glama
janorium-mcp

janorium-mcp

Official

Scale to a target drawdown

backtest_risk_scaling
Read-onlyIdempotent

Calculates the position-size multiplier that scales a backtest’s max drawdown to a target drawdown percentage, returning the multiplier, resulting return, and implied leverage.

Instructions

The position-size multiplier k that turns this run's max drawdown into targetDrawdownPct, and return and implied leverage at k.

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": {
      "backtestId": "<backtestId>",
      "targetDrawdownPct": "<targetDrawdownPct>"
    },
    "name": "backtest_risk_scaling"
  }
}

Input Schema

NameRequiredDescriptionDefault
backtestIdYes
targetDrawdownPctYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare the tool as read-only, idempotent, closed-world, and non-destructive. Beyond that, the description adds substantive behavioral context by specifying the outputs: k, return at k, and implied leverage at k, and tying them to the run's max drawdown and targetDrawdownPct. It does not discuss edge cases or error behavior, but for a read-only calculation this is useful additional context.

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?

The definition is a single, front-loaded sentence with no filler. It efficiently states the core computation and the returned values. The phrasing is slightly dense, but every part contributes to understanding the 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?

For a simple two-parameter, read-only calculation with no output schema, the description provides enough to understand what is computed and what is returned. It does not cover edge cases such as unachievable target drawdowns or invalid backtest references, but annotations and schema handle safety and validation constraints.

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 0%, so the description must carry parameter meaning. It names targetDrawdownPct and implicitly identifies backtestId via 'this run's max drawdown', clarifying the role of both inputs in the calculation. However, it does not explicitly define backtestId as the run identifier or explain targetDrawdownPct's bounds and units beyond the parameter name.

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?

The description clearly states the tool computes the position-size multiplier k that maps a backtest run's max drawdown to targetDrawdownPct, along with return and implied leverage at k. That is a specific computation and resource, making the tool distinguishable in practice. It does not explicitly contrast itself with sibling backtest tools, so it stops short of a 5.

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: use it when you need to scale position size for a given backtest run to hit a target drawdown. There is no explicit when-to-use guidance, no exclusions, and no named alternative such as backtest_monte_carlo or backtest_compare. The context is inferable but not spelled out.

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