Skip to main content
Glama

Plan a trade from your own limits (places nothing)

plan_gambit

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. Over this connector Gambit runs no model for you: YOUR OWN model does the personal work. (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: the take formed again on top of the shared take plus your facts, which are assumed true for your view only. To form it: call get_gambit_pack, form the take with the rules and output_schema in the pack, then call submit_gambit_view. (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.

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
account_valueNoaccount value in USD

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.8/5.0
Behavior5/5

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

The description discloses key behavior beyond the annotations: no order placement, no trade record, no model run, no recommendation quota, personal-layer storage with plan_id, and a daily rate limit surfaced as 429 rate_limited. It also documents specific error codes and when they occur. The annotations say readOnlyHint=false, which is consistent with storing a personal plan, so there is no contradiction.

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

Conciseness3/5

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

The description is front-loaded and organized with numbered steps, but it is very long and repeats some points about not placing orders and not being a recommendation. For a tool with four parameters, the volume of detail is higher than necessary, though much of it is useful for error handling and output interpretation.

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 no output schema, the description sufficiently explains the returned plan fields, limits, differs behavior, and error states. It is complete enough for an agent to call the tool correctly and interpret common failure modes without additional documentation.

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?

Although schema coverage is 100%, the description adds substantial meaning: risk_pct defaults to the user's trade policy or Gambit's default, account_value is not read from the portfolio and omission leaves size_usd null with a needs hint, and use distinguishes shared-view planning from the user's latest accepted view including the differs output.

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: it produces a trade plan for one ticker with entry, stop, size, and exits from the user's own limits. It also distinguishes the tool from sibling view/evidence tools by framing it as the "how would I size this?" call.

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?

It names the use case directly, explains the shared vs mine choices, describes how it fits after get_gambit_pack/submit_gambit_view, and notes that account_value must be requested from the user when absent. It also gives explicit error conditions like no_user_view and price_unavailable that tell the agent when to retry or take another path.

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