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, with a new version only when Gambit's view changes. 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) and no_change (true when nothing in the view changed). 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), observation (a news item or post attributed to the Gambit: symbol, source_types, summaries, why_now (why it was surfaced for this Gambit), attention_refs, category, horizon, and source_snapshots with the excerpt, url, publisher and source_at — attention only, not verified evidence) or judgment (an assessment entry: 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 judgment is Gambit's read of the Gambit for YOUR account: stance (recommend | watch | stand_aside), conviction (high | medium | low), summary (the written view), changes_if (what would change it), evidence_refs, user_reported_context (things you told Gambit that shaped it) and as_of. 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.)

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

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, but the description adds substantial context: shared versioned view semantics, ambiguity handling via 422 ambiguous_symbol and ref:eq:TICKER, error codes, api:read requirement, app_url behavior, and pagination mechanics. No annotation contradiction.

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

Conciseness4/5

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

The definition is front-loaded with the core purpose and organized with BY SYMBOL / BY CASE_ID / Errors sections. However, it is very long and dense, with several run-on parentheticals, so it is not maximally concise.

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, but the description exhaustively covers return fields for each view, pagination, error behavior, permissions, and app_url differences. For a complex tool with two modes and eight parameters, this is complete.

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 100%, but schema descriptions are terse; the prose adds meaningful detail: accepted symbol formats, ref:eq fallback for US stocks, case_id source, view enum meanings, limit defaults, before_version/next_cursor usage, and required ids for entry/observation views. This goes well 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 opening sentence states a specific verb/resource and two mutually exclusive modes: Gambit's shared view of a ticker by symbol, or a dated history of one of the user's Gambits by case_id. It also names list_gambits as the source for case_id, making the tool's purpose distinct and actionable.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explicitly says 'Pass exactly one of the two' and gives detailed conditions for symbol reads (any covered ticker, even without a Gambit) versus case_id reads (from list_gambits). It also covers ambiguity resolution and reporting bad views via leave_feedback, but does not explicitly say when to choose this over sibling get_gambit.

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