Skip to main content
Glama

get_risk_limits

Read-only

Fetch saved trading risk limits—max open positions, dollars at risk per trade, leverage, minimum equity, and book status—plus what-if equity or preset checks before profile changes.

Instructions

Get what this account may trade under its saved risk profile: positions at once, dollars at risk per trade at the stop, max leverage, the minimum equity to trade and whether each book can trade now, with a one-line headline. equity_usd and preset answer what-if questions (a different account size or preset) and change nothing. Use to explain the limits, or before changing the profile with update_config. To size one specific trade use size_trade; for the raw config use get_config. Needs a configured account unless equity_usd is given (else {error, no_account: true}). A book is one strategy slot the profile allows (desk or manual). Returns {headline, can_trade, max_open_positions, risk_per_trade_usd, max_leverage, books[], notes[]}.

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

Input Schema

NameRequiredDescriptionDefault
presetNoWhat-if risk preset instead of the saved one.
equity_usdNoWhat-if equity in USD instead of the account's own.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.6.1

TDQS

A4.8/5.0
Behavior5/5

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

Goes well beyond readOnlyHint=true by disclosing that the what-if parameters 'change nothing', the failure mode ({error, no_account: true}) when no account is configured, the semantics of a 'book' (one strategy slot the profile allows), and the returned key set. These are operational facts an agent cannot get from annotations or schema.

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 purpose and the returned values, then usage routing, prerequisites, and return shape in a logical order with no filler sentences. It is dense in places (parenthetical asides and a long enumeration) but every clause carries information.

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?

With no output schema, the description compensates by listing the return keys ({headline, can_trade, max_open_positions, risk_per_trade_usd, max_leverage, books[], notes[]}), and it covers the prerequisite edge case. Nothing needed to call a two-parameter read tool correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3, but the description adds real meaning: both parameters are framed as what-if inputs that answer hypothetical questions about a different account size or preset and explicitly have no side effects. That side-effect-free framing is not stated in the schema and matters for safe invocation.

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 verb and resource ('Get what this account may trade under its saved risk profile') and then enumerates the exact content: positions at once, dollars at risk per trade at the stop, max leverage, minimum equity, per-book tradability, and a headline. It is clearly distinguishable from get_config (raw config) and size_trade (single trade).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly names when to use it ('to explain the limits, or before changing the profile with update_config') and routes to two alternatives by condition: size_trade for sizing one trade, get_config for the raw config. It also gives a prerequisite rule (needs a configured account unless equity_usd is given).

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