Skip to main content
Glama

Remove one of your facts from a ticker

remove_gambit_evidence
Destructive

Remove one of YOUR facts from a ticker's personal layer (requires api:account) — the call for "take back what I said about INIT" or to correct a fact (remove it, then add the corrected one with add_gambit_evidence; a fact is never edited in place). 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. user_item_id: the fact's id, from get_gambit_facts, from add_gambit_evidence's user_item, or from user_items in get_gambit's your_view. The fact is withdrawn (kept in your history, never counted again). When Gambit had set the fact aside (it moved nothing), that is all: your view stays as it is, including a view your own model submitted, and the answer carries kept_view true. Otherwise your view goes back to Gambit's and, when other facts remain, Gambit runs your update again so they apply on its current view (a view your own model submitted is then replaced by the one Gambit forms). Returns withdrawn (the user_item_ids withdrawn) and your_view (status ready, same_as_shared, forming or unavailable, as add_gambit_evidence answers it; check it before telling the user the fact is gone). Confirm with the user before removing. 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); 404 unknown_fact when the id is not one of your active facts on this ticker; 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>",
      "user_item_id": "<user_item_id>"
    },
    "name": "remove_gambit_evidence"
  }
}

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
user_item_idYesthe fact's user_item_id (a positive id; a pack id such as -4 is fact 4)

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?

Annotations already flag destructiveHint=true and idempotentHint=false, but the description goes well beyond them: the fact is withdrawn but kept in history and never counted again, the user's view may revert to the shared view or be re-formed, a self-submitted model view is replaced, kept_view is returned when nothing moved, and auto-execute may trigger a trade on a changed view. It also discloses the api:account requirement. That is unusually complete disclosure of side effects for a destructive mutation.

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 opening two sentences are well front-loaded and the remainder is padded with a multi-section onboarding tour of Gambit (add, personal view mechanics, what-if, plan) that is not needed to invoke a two-parameter delete. For a tool of this simplicity the description is roughly ten times longer than necessary, and the key operational facts are buried in the middle of a narrative.

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?

There is no output schema, so the description carries the return contract, and it does: withdrawn user_item_ids plus your_view with its ready/same_as_shared/forming/unavailable statuses, and a note to check it before telling the user the fact is gone. Combined with the error catalogue and no-order statement, nothing needed to call this destructive tool safely 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 both parameters are already documented, and the description adds genuine meaning for user_item_id by naming its three provenance paths (get_gambit_facts, add_gambit_evidence's user_item, user_items in get_gambit's your_view). It also clarifies the pack-id convention in prose. Symbol handling is left to the schema, which is adequate.

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 opening clause names a specific verb and resource ('Remove one of YOUR facts from a ticker's personal layer'), states the required scope (api:account), and immediately contrasts with reset_gambit_view ('takes back every fact') and add_gambit_evidence. An agent can distinguish this from siblings without opening a 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?

It gives explicit trigger scenarios ('take back what I said about INIT', correcting a fact by removing then re-adding), names the sibling alternative reset_gambit_view with its differing scope, instructs to confirm with the user before removing, and enumerates error conditions (409, 404, 422, 503) with remedies. Guidance on when to use versus the alternative is unambiguous.

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