Skip to main content
Glama

Get a ticker's evidence pack for your own model

get_gambit_pack
Read-onlyIdempotent

The evidence pack for one ticker, so YOUR OWN model can form a view of it (requires api:read). Optional: Gambit already keeps your view on its side from the facts you add; use this only when the user wants their own model's view. 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. Returns based_on_version (the shared version the pack is built from), pack (the shared take with everything behind it: its levers with state, what is priced and thresholds, its tests with watch ids, macro, mechanics and the analyst's ledger; the market numbers; and items, each with its item_id: the sources the shared take rests on, plus your own facts marked kind user with negative ids), rules (Gambit's analyst method; items marked kind user are the user's own information: assume they are true and say so), output_schema (the JSON schema of the take to return) and submit_with (submit_gambit_view). Gambit runs no model for this call. Next: form the take with your model, following the rules and output_schema, cite only ids from this pack (the item_ids of items, and the ids the shared take itself cites, which can be older than items), and pass the JSON object to submit_gambit_view with your model's name and this pack's based_on_version. 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_reads_disabled while these reads are 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>"
    },
    "name": "get_gambit_pack"
  }
}

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.3/5.0
Behavior5/5

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

Despite annotations already declaring readOnlyHint, idempotentHint and openWorldHint=false, the description adds substantive behavior: the api:read scope requirement, "Gambit runs no model for this call," the full return shape (based_on_version, pack, rules, output_schema, submit_with), and the 409/404/422/503 error semantics with recovery actions. This goes well beyond what the structured annotations convey.

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 sentence is well front-loaded, but the body is a dense wall of text that spends most of its length narrating the entire Gambit view lifecycle — fact expiry, check-by dates, resets, taking back facts — which is largely irrelevant to invoking this read tool. Nested parentheticals and run-on sentences bury the two things the caller actually needs (form the take, then submit with ids and based_on_version).

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 single-parameter read tool with no output schema, the description is complete: it enumerates the return fields, explains which ids are citable, specifies the exact handoff to submit_gambit_view including the required model name and based_on_version, and lists every error condition with a remedy. Nothing an agent needs in order to call it correctly 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?

With 100% schema coverage the single symbol parameter is already documented, so the baseline is 3. The description earns an extra point by adding error-handling semantics the schema lacks: 422 ambiguous_symbol returns candidates and the caller should "call again with one candidate as the symbol," plus 404 unknown_symbol behavior. Format syntax itself is left to the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

"The evidence pack for one ticker, so YOUR OWN model can form a view of it" names the resource and the reason it exists, and the description contrasts it with Gambit's own server-side view ("you do not need your own model for it"). The specific retrieval verb is implied rather than stated, and the distinction from the sibling get_gambit only surfaces obliquely inside the 409 error text, so it falls short of a clean 5.

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 explicit exclusion: "use this only when the user wants their own model's view," after noting Gambit already keeps the view server-side from added facts. It then names the follow-on alternative ("call get_gambit_pack, form the take... then call submit_gambit_view") and the fact-recording path via add_gambit_evidence, so an agent knows both when to call and when not to.

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