Skip to main content
Glama

Submit your own model's view of a ticker

submit_gambit_view

Submit the view YOUR OWN model formed from get_gambit_pack (requires api:account). view is a fresh take in the pack's output_schema (at most 6 levers and 6 tests; claim_horizon next_event, 1_month or 3_months, any other horizon is rejected), not a stored view read back from get_gambit: a stored view carries more tests and older citations and is rejected. To go back to Gambit's view use reset_gambit_view. Optional: Gambit already keeps your view on its side from the facts you add; submit only when the user wants their own model's view. Once accepted, it is your view, and Gambit moves it on its side with each new shared version and fact. 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. view: the take your model produced, as a JSON object matching the pack's output_schema. model (1-80 characters): your model's name, for example claude-opus-5.5; the stored view is labelled with it. based_on_version: the based_on_version of the pack your model used; when the shared view has moved on since, the answer is 409 pack_changed: call get_gambit_pack again and form the view again. Gambit checks the take the way it checks its own: it must parse, cite only ids from the pack (your own facts and the shared take's own citations included), keep price levels out of the shared tests (they belong in price_levels), give no price targets, market timing or rate forecasts of its own, and say why when it sees no edge. Gambit does not smooth it toward the shared view: it is your model's view. It is stored in YOUR personal layer, accepted or rejected, and never changes the shared view. Returns status (accepted: it is now your view; rejected: it is stored but is not your view), user_view_id, produced_by, based_on_version, the view as rendered (sources are shown only for items of the pack), differs (how it differs from the shared view, in plain lines), diff (the same difference as structure: lean with main, user and difference, shown_lean, the levers and pending tests only one view holds, the shared ones that differ with both values, and empty true when the two views match) and problems. When status is rejected, fix each problem and submit again; a view that cannot be read at all is rejected the same way, with view null. 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 pack_changed; 422 reserved_model_name when model is "gambit"; 503 gambit_personal_disabled while the personal layer is switched off. 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>",
      "view": "<view>",
      "model": "<model>",
      "based_on_version": "<based_on_version>"
    },
    "name": "submit_gambit_view"
  }
}

Input Schema

NameRequiredDescriptionDefault
viewYesthe view your model produced, as a JSON object matching output_schema
modelYesyour model's name, e.g. claude-opus-5.5
symbolYesa ticker such as BTC or NVDA, or an exact id such as xyz:GOOGL or ref:eq:IP, as for get_gambit
based_on_versionYesthe based_on_version of the pack your model used (from get_gambit_pack)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the annotations, it discloses that the view is stored in the caller's personal layer, never changes the shared view, and is validated against the pack's rules. It also documents rate limiting, 409 pack_changed recovery, rejection behavior, and the important auto-execute side effect that a changed view may cause Gambit's strategy to trade.

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 first sentence is well front-loaded, but the description then expands into a very long, repetitive walkthrough of the whole Gambit toolchain, including add_gambit_evidence, what_if_gambit, and plan_gambit. Key invocation details are buried, and the personal-layer/shared-view point is restated multiple times.

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 complex mutation tool with no output schema, it thoroughly explains return fields, rejection handling, error statuses, validation rules, and side effects. There is little an agent would need to know before calling it that 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 complete, but the description adds real meaning: view must match the pack output_schema, levers and tests are capped, claim_horizon is restricted, and based_on_version produces a 409 if the shared view has moved. The model parameter's labeling and reserved-name behavior are also clarified beyond the schema.

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 opens with a specific verb and resource: submit your own model's view formed from get_gambit_pack. It explicitly contrasts this with a stored view from get_gambit and with reset_gambit_view, so the agent can distinguish it from siblings without opening schemas.

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 states the prerequisite api:account, says the action is optional, and gives the exact condition for using it: only when the user wants their own model's view. It also names the alternatives, including letting Gambit keep the view automatically and using reset_gambit_view to go back.

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