Skip to main content
Glama

Get a Gambit

get_gambit
Idempotent

Gambit's view of one ticker (pass symbol), or one of YOUR Gambits in full (pass case_id). Pass exactly one of the two. BY SYMBOL (BTC, HYPE, NVDA, or an exact Hyperliquid id such as xyz:GOOGL): Gambit's view is ONE shared, versioned view per ticker: the same view for every user. A new version does not mean the view changed: every accepted run on the ticker (a scheduled review, or new stories to judge) writes one, even when it only refreshes the market numbers. no_change true in get_gambit_history marks those versions, and gambit_changes leaves them out. Reading by symbol works for any ticker Gambit covers, a Hyperliquid listing or a US stock, even when you have no Gambit on it. A bare ticker that names a Hyperliquid listing (often a crypto perp) and also a US stock with no Hyperliquid listing reads the Hyperliquid one. Check subject_type and display_symbol against what the user meant; pass ref:eq:TICKER (for example ref:eq:IP) to read the US stock. A ticker that stays ambiguous answers 422 ambiguous_symbol with candidates (subject ids such as asset:crypto:IP); call again with one candidate as the symbol. Your answer to the user starts with since_you_last_looked: what changed in the view since this user last read this ticker, why, and what caused it (or first_look on a first read). The response also carries subject_id, display_symbol, subject_type, version, as_of and generated_at; view (the headline and summary, our view against what's priced, the horizon, what produces the price (engine), positioning, the levers as reasons — each with its state, what the price assumes about it, our read, the threshold that would change our mind, and its sources, plus driver (subject_id and version) on a lever that cites Gambit's shared take of a macro driver such as the Fed path or oil — the macro forces with this asset's exposure, instrument mechanics, the case against, what would prove us wrong and what would confirm it with dates (each tied to a lever_id), the next dated events, how likely we are to be wrong, what we can't judge, and the map of what is priced when there is no edge; price_levels only when you pass price_levels true); new_since_view (official or wire news published after the view was formed); freshness (status fresh, cached or unavailable); and what_would_change_our_view (the dated conditions that would change it, each with overdue true when its date has passed and Gambit has not yet recorded the result, and the case against). reasoning (the analyst's ledger against the previous version — what happened to each lever and test, with sources — the noise it set aside and why, its research trail: which data it read, which searches it ran and which pages it read, and dig_further: where to go for more). When the user pushes back, test their claim against the levers' thresholds and what_would_change_our_view and say what evidence would change the view; do not just restate it. To score a new hypothetical event, call what_if_gambit. your_view (only when the user has a view of their own: the take Gambit keeps for them from the facts they added with add_gambit_evidence, or one their own model submitted; absent while their take is the same as the shared one) carries that view, produced_by (who formed its judgment: gambit, or the user's model name; a submitted view stays theirs while Gambit's updates leave its judgment unchanged, with updated_by_gambit true), user_items (the facts that still count), differs (plain lines) and diff (the levers, pending tests and lean where it differs from the shared view; empty true when they match). Gambit moves that view on its side with each new shared version, so read it here after add_gambit_evidence answered forming. your_gambit (when the personal layer is on): the user's live Gambit on this ticker that their facts and own view belong with (case_id, title, note, monitoring_status; null when they have none), and your_facts (their active facts on it: user_item_id, claim, status, check_by, url, added_at). The note is the user's own words and never moves any view: to make it count, add it as a fact with add_gambit_evidence. followed is true when the user follows this ticker (one of their Gambits on it is live). mark_seen=true (the default) records that this user has now seen this version on a ticker they follow, so the next read reports only later changes. A read never follows a ticker: on a ticker the user does not follow, mark_seen records nothing. When followed is false, offer to follow the ticker with create_gambit. Pass mark_seen=false to read without recording the version. since (a version number such as 3, or an ISO date or time such as 2026-10-14 or 2026-10-14T13:30:00Z; a time with no offset is UTC, a date alone means the end of that UTC day, so the view as it stood on that day) asks what the view was then and what changed since: Gambit picks that version, or the latest version published at or before that time, and adds then (that version's number, as_of, shown_lean, lean_words, headline, summary, its levers as reasons with their sources, and its pending tests: prove_us_wrong and would_strengthen) and since (what changed from that version to the latest and why, in the same form as since_you_last_looked; anchor_before_first true means the time was before Gambit's first view was published, so it starts from the first version). When you pass since, start your answer with then and since (the change from that point), not since_you_last_looked. A read with since never records a version as seen, whatever mark_seen says. For the price move since each version, call get_gambit_history. A ticker with no view yet answers status building and is queued (queuing an asynchronous Gambit view build on first read of an unseen symbol): read it again later instead of polling in a tight loop. To report a view that looks wrong, call leave_feedback (needs api:account) with category data_quality and area gambits, and name the subject_id and version in the message. Errors: 404 unknown_symbol; 422 ambiguous_symbol with candidates; 422 invalid_since when since is neither a version number nor an ISO date or time; 404 unknown_version when since names a version that does not exist; 503 gambit_reads_disabled while these reads are switched off. A symbol read has no app_url. BY CASE_ID (from list_gambits or get_tracking_updates): everything list_gambits returns except take, plus: case_seed — what this Gambit follows (note: the user's own words; monitoring_question, monitoring_lenses, relationship_focus, horizon, change_criteria, and the seed summary); provenance (where it came from: discovery, mandate_activity, market_opportunity, chat or api); original_thesis (the advisory the Gambit started from, when it came from one) and current_advisory (the advisory behind the newest judgment, when known); mandate_lineage_id; the opportunity-tracking record (opportunity_first_tracked_at, opportunity_first_price, opportunity_last_result); judgments — the dated log, newest first (each entry's id, trigger_kind, update_category, judgment_before / judgment_after, delta_summary, material flag, evidence_refs, captured_price and created_at; judgment_count is the true total); and gambit, Gambit's shared take of the Gambit's asset (subject_id, version, as_of, the same view, since_you_last_looked, what_would_change_our_view and feedback; null when Gambit has no view of the asset; a case_id read never records it as seen and runs no freshness check, so it has no new_since_view: read by symbol for news since the view was formed). When the personal layer is on, gambit also carries the user's own layer on that asset: your_facts (their active facts: user_item_id, claim, status, check_by, url, added_at; remove one with remove_gambit_evidence), your_view (their own view of it, as the symbol read gives it; null while it is the same as Gambit's) and note_role (the note in case_seed is their words and never moves a view). gambit is Gambit's view; lead with it, not with the log. A Gambit records that YOU follow an asset, with your own note; it has no stance of its own. Gambit's view of the asset is its shared take (take, or gambit on one Gambit). A judgment is one entry in an older Gambit's log: summary, changes_if, evidence_refs, user_reported_context (things you told Gambit) and as_of. A Gambit opened from November 2026 on has no log entries (current_judgment null, judgment_count 0, judgments empty), and a prediction-market contract that expires only changes its state. It carries no stance or conviction; do not present it as Gambit's view. A Gambit that is not yours answers 404, exactly like one that does not exist. A case_id read carries app_url, this Gambit's screen. (Requires api:read.)

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_gambit"
  }
}

Input Schema

NameRequiredDescriptionDefault
sinceNosymbol reads only: a version number (3) or an ISO date or time (2026-10-14, 2026-10-14T13:30:00Z); adds then (the view at that version) and since (what changed from it to now). Never records a version as seen
symbolNoa ticker such as BTC or NVDA, an exact id such as xyz:GOOGL or ref:eq:IP (the US stock), or a candidate subject id from ambiguous_symbol; pass symbol or case_id, not both
case_idNoa Gambit id from list_gambits (UUID); pass case_id or symbol, not both
mark_seenNosymbol reads only, default true: record that the user has now seen this version (on a ticker they follow; a read never follows a ticker)
price_levelsNodefault false: add the price-level add-on (key levels, and wrong-if / confirms-if closes with dates) when the view has one

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / mark_seen / description
      Previous value: -"symbol reads only, default true: record that the user has now seen this version"New value: +"symbol reads only, default true: record that the user has now seen this version (on a ticker they follow; a read never follows a ticker)"
  2. Changed1 schema field changed
    • addedInput schema / properties / since
      Added value: +{
      +  "description": "symbol reads only: a version number (3) or an ISO date or time (2026-10-14, 2026-10-14T13:30:00Z); adds then (the view at that version) and since (what changed from it to now). Never records a version as seen",
      +  "maxLength": 64,
      +  "minLength": 1,
      +  "pattern": "^[0-9A-Za-z:.+-]+$",
      +  "type": "string"
      +}
  3. Changed1 schema field changed
    • addedInput schema / properties / price_levels
      Added value: +{
      +  "description": "default false: add the price-level add-on (key levels, and wrong-if / confirms-if closes with dates) when the view has one",
      +  "type": "boolean"
      +}
  4. Changed4 schema fields changed
    • changedInput schema / properties / case_id / description
      Previous value: -"a Gambit id from list_gambits (UUID)"New value: +"a Gambit id from list_gambits (UUID); pass case_id or symbol, not both"
    • addedInput schema / properties / mark_seen
      Added value: +{
      +  "description": "symbol reads only, default true: record that the user has now seen this version",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / symbol
      Added value: +{
      +  "description": "a ticker such as BTC or NVDA, an exact id such as xyz:GOOGL or ref:eq:IP (the US stock), or a candidate subject id from ambiguous_symbol; pass symbol or case_id, not both",
      +  "pattern": "^[A-Za-z0-9][A-Za-z0-9._:-]{0,63}$",
      +  "type": "string"
      +}
    • removedInput schema / required
      Removed value: -[
      -  "case_id"
      -]
  5. Added

TDQS

A4.6/5.0
Behavior5/5

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

Goes well past the annotations (readOnlyHint=false is consistent with the disclosed mark_seen write and build-queue side effect). It discloses the asynchronous build queued on first read of an unseen symbol, the exact error contract (404 unknown_symbol, 422 ambiguous_symbol with candidates, 422 invalid_since, 404 unknown_version, 503 gambit_reads_disabled), the permission requirement (api:read, api:account for feedback), and that a case_id read carries app_url while a symbol read does not.

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?

Effectively one enormous run-on block of roughly a thousand-plus words with no headings or line breaks, mixing routing rules, response field walkthroughs, personal-layer semantics and error codes. The first sentence is well front-loaded, but the agent must wade through dense, repetitive prose to reach the operational rules.

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 tool with no output schema and two very different modes, the description covers the return shape for both (since_you_last_looked, view subfields, freshness, what_would_change_our_view, your_view/your_gambit/your_facts, and the case_id extras such as case_seed, judgments, provenance), plus side effects and error codes. Nothing needed to invoke 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?

Schema coverage is 100%, so the baseline is 3, but the description genuinely adds meaning: since accepts a version number or ISO date/time with a stated UTC convention and end-of-day rule, adds then/since, and never records a seen version; symbol ambiguity resolution flows (ref:eq:, subject ids like asset:crypto:IP); mark_seen only records on followed tickers. It stops short of nothing important, but much of the prose repeats schema text verbatim.

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 sentence names the exact resource and both access modes: Gambit's shared view of one ticker by symbol, or one of the user's own Gambits in full by case_id. It is clearly distinguishable from siblings like get_gambit_history (price move since each version), what_if_gambit (hypotheticals) and list_gambits (id source), which the text itself names.

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?

Explicit routing is given for nearly every situation: pass exactly one of symbol/case_id, use ref:eq:TICKER for a US stock, retry with a candidate from ambiguous_symbol, call what_if_gambit to score a hypothetical, get_gambit_history for price moves, add_gambit_evidence to make a note count, create_gambit to follow an unfollowed ticker, and leave_feedback to report a bad view. Exclusions are stated too (a case_id read never records as seen and runs no freshness check).

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