Skip to main content
Glama

Plan a trade from your own limits (places nothing)

plan_gambit

Three timeframe alternatives (LTF hours–days, MTF days–weeks, HTF months–years), with optional timeframe/source_version selection and private entry/stop/target refinement. Refined sizing is recalculated; no orders are placed. A trade plan for one ticker from YOUR own limits (requires api:recommend) — the call for "how would I size this?". The chain for one ticker. Everything it stores is in YOUR personal layer: the shared view never changes because of it. Gambit forms your view on its side: you do not need your own model for it. (1) Add data: add_gambit_evidence stores a fact you know. It is labelled unconfirmed until Gambit confirms it from an official or wire source that states it; a confirmed fact's source joins the shared evidence, and the shared view uses it on its normal run. (2) Your view: your own take, which Gambit keeps for you. It starts as the shared take. Each fact you add, each new shared version and each update you ask for moves it: Gambit's per-story step judges your new facts and the shared news since your last update against your take and applies its verdicts. A fact that changes a lever adds a test to your take: wrong if the fact is not confirmed by its check-by date. A fact that expires unconfirmed after its check-by date leaves no trace: when Gambit had set it aside (it moved nothing), your view stays as it is; otherwise your take points back to the shared take and Gambit applies your remaining facts again on it, and with no fact left you follow the shared view. remove_gambit_evidence takes one fact back; reset_gambit_view takes back every fact. When your take ends up the same as the shared one, you follow the shared view again. To use your own model's view instead (optional): call get_gambit_pack, form the take with the rules and output_schema in the pack, then call submit_gambit_view; Gambit then moves that view the same way. (3) What if: what_if_gambit gives the view if something happened; when the question matches a dated condition the view already lists, the answer is precomputed and no model runs; otherwise it returns the pack with the event added, for your model to answer. (4) Plan: plan_gambit gives entry, stop, size and exits from your own limits. A plan is not a recommendation to trade and places no order. use: shared (plan from the shared view) or mine (plan from your latest accepted view while get_gambit still shows it; the answer also gives the size from the shared view, so the difference your view makes is explicit: differs.line says "With your information" for a view Gambit formed from your facts, and "With your view (formed by )" for one your own model formed). risk_pct (optional): the percent of the account to risk; by default your trade policy's, else Gambit's default. account_value (optional, USD): Gambit does not read it from your portfolio; without it the plan has no size (size_usd null, and needs lists account_value), so ask the user for it. The direction follows the view's lean. With no real lean (|shown_lean| below 1) the answer is action no_trade, with why. Otherwise: entry (the latest price), stop (from the ticker's realized volatility), size_usd and risk_usd (sized so that a stop-out loses about risk_pct of the account; capped_by_max_position is true when your maximum position size cut it, and capped_at_account_value when the size stopped at the whole account value, so risk_usd is then less than risk_pct), exits (the view's dated "wrong if" conditions, plus the stop), check_by (the earliest confirm-by date of your facts), based_on, limits_used, differs and disclaimer. Price levels belong to the plan, never to the view. Tell the user it is a plan from their own limits and not a recommendation to trade. It places no order, writes no trade record, runs no model and uses no recommendation quota; the plan is kept in your personal layer (plan_id), and a daily limit applies (429 rate_limited with retry_after). Errors: 409 gambit_building when Gambit has no view of the ticker yet (get_gambit by symbol queues it; try again later); 404 unknown_symbol; 422 ambiguous_symbol with candidates (call again with one candidate as the symbol); 409 no_user_view when use is mine and you have no current accepted view (add data or submit a view again); 409 price_unavailable or volatility_unavailable when the plan cannot set its levels; 503 gambit_personal_disabled while the personal layer is switched off.

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": {
      "symbol": "<symbol>",
      "use": "<use>"
    },
    "name": "plan_gambit"
  }
}

Input Schema

NameRequiredDescriptionDefault
useYesshared: plan from the shared view; mine: from your latest accepted view
symbolYesa ticker such as BTC or NVDA, or an exact id such as xyz:GOOGL or ref:eq:IP, as for get_gambit
risk_pctNopercent of the account to risk on this plan
timeframeNoSelect a timeframe; all alternatives remain in the response
refinementNo
account_refNoOnly manual account inputs are currently supported; this is not a connected-account selector
account_valueNoaccount value in USD
source_versionNoRequired with timeframe; accepted shared version being selected
source_user_view_idNoRequired when selecting from mine; pins the private view identity

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedInput schema / properties / account_ref
      Added value: +{
      +  "const": "manual",
      +  "description": "Only manual account inputs are currently supported; this is not a connected-account selector",
      +  "type": "string"
      +}
    • addedInput schema / properties / refinement
      Added value: +{
      +  "additionalProperties": false,
      +  "properties": {
      +    "entry": {
      +      "exclusiveMinimum": 0,
      +      "type": "number"
      +    },
      +    "stop": {
      +      "exclusiveMinimum": 0,
      +      "type": "number"
      +    },
      +    "target": {
      +      "exclusiveMinimum": 0,
      +      "type": "number"
      +    }
      +  },
      +  "required": [
      +    "entry",
      +    "stop",
      +    "target"
      +  ],
      +  "type": "object"
      +}
    • addedInput schema / properties / source_user_view_id
      Added value: +{
      +  "description": "Required when selecting from mine; pins the private view identity",
      +  "exclusiveMinimum": 0,
      +  "type": "integer"
      +}
    • addedInput schema / properties / source_version
      Added value: +{
      +  "description": "Required with timeframe; accepted shared version being selected",
      +  "exclusiveMinimum": 0,
      +  "type": "integer"
      +}
    • addedInput schema / properties / timeframe
      Added value: +{
      +  "description": "Select a timeframe; all alternatives remain in the response",
      +  "enum": [
      +    "ltf",
      +    "mtf",
      +    "htf"
      +  ],
      +  "type": "string"
      +}
  2. Added

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the annotations, the description discloses that no order is placed, no trade record is written, no model runs, no recommendation quota is used, and a plan_id is stored in the personal layer. It also documents the daily rate limit, 429 behavior with retry_after, and several specific error conditions.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is far too long for the task and includes extensive detail about the broader evidence and view lifecycle that is not necessary for invoking plan_gambit. It has some structural markers via numbered sections and error lists, but the overall size and detours hurt front-loading and conciseness.

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?

Given the tool's complexity, nine parameters, nested refinement object, and lack of an output schema, the description is thorough. It covers outputs such as entry, stop, exits, check_by, differs, limits_used, and disclaimer, along with relevant error handling.

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

Parameters5/5

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

The description adds substantial meaning beyond the schema: use selects shared versus mine, risk_pct defaults to the trade policy or Gambit default, and account_value is not read from the portfolio so omitting it yields size_usd null and a needs list. It also explains direction, no_trade behavior, and private refinement semantics.

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 states a specific verb and resource: "plan_gambit gives entry, stop, size and exits from your own limits." It distinguishes the tool from a recommendation or order by saying "A plan is not a recommendation to trade and places no order," and it clarifies the shared-versus-mine planning modes.

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?

It gives clear usage context, including "the call for 'how would I size this?'" and explains when to use the shared view versus your own view. It does not explicitly compare against other planning siblings such as get_daily_move_plan, but the intended use case and exclusions from trade execution are clear.

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