Skip to main content
Glama

Get a Gambit's history

get_gambit_history
Read-onlyIdempotent

The history of Gambit's view of one ticker (pass symbol), or the dated history of one of YOUR Gambits (pass case_id). Pass exactly one of the two. BY SYMBOL (BTC, NVDA, 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. Returns subject_id, display_symbol and its accepted versions, newest first: each version's number, as_of, the headline and summary at that version, change_lines (what changed in our thinking, in the analyst's words), note, verdict_moved, ledger (what happened to each lever and test of the version before, with sources), noise (what was set aside and why), no_change (true when nothing in the view changed), close (the last close Gambit recorded with that version, or null) and move_since (how the price moved from that close to the newest version's close: percent, to_version, and close_as_of, the time of that newest close; null when either close is missing; every page measures to the same newest version). Page with limit (1-100, default 20) and before_version (next_before_version from the previous page; null means there are no older versions). view, entry_id, observation_id and cursor are case_id reads only. 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; 503 gambit_reads_disabled while these reads are switched off. A symbol read has no app_url. BY CASE_ID (from list_gambits): view=history (default): the full timeline, newest first, as items of kind opportunity (a captured market opportunity entry, or a shared card of the Gambit's ticker, any past airing, from before the follow too, at most one per detector, ticker and UTC day, dated by when it first aired: captured_price null; its entry.id reads with view=entry), observation (a news item or post attributed to the Gambit: symbol, source_types, summaries, why_now (Gambit's own short account of the source and why it was surfaced for this Gambit), attention_refs, category, horizon, and source_snapshots with the url, publisher, author and source_at — the source excerpt, and any summary that copies it, are not included, open url to read the source; attention only, not verified evidence) or judgment (a log entry, with no stance: trigger_kind, update_category, judgment_before / judgment_after, delta_summary, material, evidence_refs, captured_price, created_at). view=entries: only the captured opportunity entries (opportunity_id, subject_id, instrument_ids, captured_at, source_at, historical, explicitly_saved, captured_price, and source_snapshot with the public headline, detail and evidence). view=entry: one entry, by entry_id. view=observation: one observation, by observation_id (the observation_id a history item carries). history and entries page with limit (1-100, default 50) and the next_cursor from the previous page. 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. A case_id read carries app_url, the Gambit's screen opened on the entry or observation when you asked for one. (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_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
viewNocase_id reads only
limitNosymbol reads, and case_id history and entries
cursorNocase_id history and entries only: next_cursor from the previous page
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
entry_idNoREQUIRED for view=entry
before_versionNosymbol reads only: next_before_version from the previous page
observation_idNoREQUIRED for view=observation

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changed
    • addedInput schema / properties / before_version
      Added value: +{
      +  "description": "symbol reads only: next_before_version from the previous page",
      +  "maximum": 2147483647,
      +  "minimum": 1,
      +  "type": "integer"
      +}
    • 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"
    • changedInput schema / properties / cursor / description
      Previous value: -"history and entries only: next_cursor from the previous page"New value: +"case_id history and entries only: next_cursor from the previous page"
    • changedInput schema / properties / limit / description
      Previous value: -"history and entries only"New value: +"symbol reads, and case_id history and entries"
    • 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"
      +}
    • addedInput schema / properties / view / description
      Added value: +"case_id reads only"
    • removedInput schema / required
      Removed value: -[
      -  "case_id"
      -]
  2. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare a safe read, but the description adds substantial behavior: the view is a shared versioned object, no_change marks versions where only market numbers refreshed, gambit_changes omits them, symbol reads have no app_url, case_id reads do, and auth requires api:read. It also discloses error codes including 404, 422 ambiguous_symbol with candidates, and 503 gambit_reads_disabled.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The main two-mode distinction is front-loaded, but the description becomes a very long dense block with repeated caveats and nested return-field enumeration. Much of it earns its place given the tool's complexity, but it is hard to scan and could be structured into shorter sections without losing behavioral detail.

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 an eight-parameter read with no output schema, the description is unusually complete: it explains both modes, pagination, return fields, version semantics, ambiguous ticker handling, ownership 404 behavior, auth, and error cases. An agent has enough information to invoke this correctly in either mode.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is already 100%, yet the description adds meaning well beyond it: view values are defined by what they return, limit defaults differ by mode (20 for symbol, 50 for history/entries), cursor and before_version are tied to specific next-token fields, and symbol accepts tickers, exact ids, ref:eq: forms, and candidate subject ids.

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 states a specific retrieval operation and distinguishes its two modes precisely: history of Gambit's shared view by ticker versus dated history of the user's own Gambit by case_id. An agent can immediately tell what is being fetched and which identifier selects which mode.

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 explicitly says to pass exactly one of symbol or case_id, identifies list_gambits as the source of case_id, explains symbol reads work even without owning a Gambit, and gives concrete ambiguity handling via ref:eq:IP or a candidate subject id after a 422. It also routes data-quality complaints to leave_feedback rather than treating this as a reporting tool.

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