Skip to main content
Glama

Reset your view of a ticker to Gambit's

reset_gambit_view
Destructive

Reset YOUR view of one ticker to Gambit's shared view (requires api:account) — the call for "go back to Gambit's take on INIT". 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. Every active fact you added on the ticker is withdrawn (kept in your history, never counted again), and a view your own model submitted stops being yours. Your Gambit and its note are unchanged. Returns withdrawn (the user_item_ids of the facts withdrawn) and your_view: status same_as_shared when the reset is done, or unavailable when it could not run now (nothing changed: try again later, and never tell the user it is reset). Confirm with the user before resetting: it cannot be undone except by adding the facts again. 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); 503 gambit_personal_disabled while the personal layer is switched off. Gambit runs no model for this call. This call places no order itself. It can change your own view, and when the user's auto-execute switch (Agent Config) is on, Gambit's take strategy acts on a changed view as on any other: it may then trade within the user's limits. Say so before this call when the switch may be on.

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>"
    },
    "name": "reset_gambit_view"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolYesa ticker such as BTC or NVDA, or an exact id such as xyz:GOOGL or ref:eq:IP, as for get_gambit

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

Goes well past the annotations: it discloses that the shared view is never modified, that withdrawn facts are kept in history but never counted again, that a self-submitted view stops being yours, that the action is irreversible except by re-adding facts, the exact return payload ('withdrawn' plus 'your_view' status same_as_shared or unavailable with retry-later semantics), the four error codes with recovery steps, and the auto-execute side effect that may trade. Annotations (destructiveHint=true, idempotentHint=false) are consistent, and the description adds the operational consequences they cannot express.

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 text is a wall of prose in which most of the bulk explains the whole Gambit product (adding evidence, how the personal take evolves, what-if, plans) rather than this tool. The core reset semantics — what is withdrawn, what is returned, which errors occur — sit near the end, after several paragraphs of unrelated context, so the definition is badly front-loaded and overlong for a one-parameter call.

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?

For a destructive, one-parameter mutation with no output schema, the definition covers return shape, error codes and recovery, irreversibility, prerequisite scopes, and the downstream auto-execute risk. Nothing an agent needs in order to call it safely is missing.

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 coverage is 100% and already documents the symbol formats (ticker, xyz:GOOGL, ref:eq:IP), so the baseline is 3. The description adds only marginal param meaning beyond that — the 422 ambiguous_symbol behavior telling the caller to retry with one of the returned candidates — which is useful but limited to a single argument.

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 ('Reset YOUR view of one ticker to Gambit's shared view') and immediately distinguishes it from the sibling it can be confused with: 'remove_gambit_evidence takes one fact back; reset_gambit_view takes back every fact.' An agent can pick between the two without opening either schema.

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?

Gives explicit trigger conditions ('go back to Gambit's take on INIT'), alternatives (remove_gambit_evidence for one fact; submit_gambit_view for a model-built view), a precondition ('requires api:account'), and an instruction to confirm with the user first. The guidance is scattered through the text but every element an agent needs to decide is present.

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