Skip to main content
Glama

Get Gambit tracking updates

get_tracking_updates
Read-onlyIdempotent

What changed across ALL of YOUR Gambits, newest first — the call for "what changed on my Gambits". Each item names case_id, case_title, case_state, monitoring_status and occurred_at, and is one of three kinds when position alerts are enabled. kind=position_alert: a material underlying-asset update for a verified position matching an actively tracked idea; position_alert carries alert_id, causes across LTF/MTF/HTF and preferred_timeframe. It never claims contract-level option PnL or authorizes an order. kind=opportunity: Gambit captured a market opportunity for that Gambit; entry.source_snapshot carries the public headline, detail, evidence and source_refs, entry.captured_price the price at capture, and entry.historical true marks context from before tracking started. kind=judgment: a new entry in an older Gambit's log; it is not Gambit reassessing the asset (changes in Gambit's view come in gambit_changes). judgment.trigger_kind says why (creation | refresh | shock | chat | manual), judgment.update_category is news or assessment, judgment.material true marks an entry worth telling the user, judgment.judgment_before / judgment_after are the entry before and after, judgment.delta_summary says what changed and why, and judgment.evidence_refs / captured_price / created_at record when and on what. Every item also carries note (the user's own words on that Gambit) and take (Gambit's shared take of its asset, as in list_gambits). 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. Page with limit (1-100, default 20) and the next_cursor from the previous page. include_gambit_changes (default false) also returns the changes in Gambit's view of the tickers you follow (the assets of your live Gambits, and only those; a live Gambit is open or watching with tracking on. A get_gambit read never starts a Gambit; create_gambit does. A Gambit on the ticker in any other state, including stopped, dismissed, executed or expired, ends the follow, and a later read does not restart it) since you last looked: 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. gambit_changes is { items, has_more }. Each item has subject_id, display_symbol, version, as_of, headline, first_look, change_lines (what changed and why) and cause_items (the sources behind it), newest first. first_look true means you follow the ticker but never marked it seen (a get_gambit read by symbol with mark_seen true, or opening its Gambit in the app): its changes count from when you started following it, not from a last look, and they come back on every call until it is marked seen; do not call them new. has_more true means older changes were left out. With it the answer is { tracking_updates, gambit_changes }; when the Gambit changes read fails, gambit_changes is null and gambit_changes_error says why. Without it the answer is the tracking updates alone. The response carries app_url, the Tracking 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_tracking_updates"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
cursorNonext_cursor from the previous page
include_gambit_changesNodefault false; true also returns gambit_changes for the tickers you follow

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / include_gambit_changes
      Added value: +{
      +  "description": "default false; true also returns gambit_changes for the tickers you follow",
      +  "type": "boolean"
      +}
  2. Added

TDQS

A3.6/5.0
Behavior4/5

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

The annotations already cover read-only/safe/idempotent, and the description adds substantial non-obvious behavior: position_alert never claims contract-level PnL or authorizes an order, gambit_changes is one shared view per ticker so a version does not mean a change, no_change versions are excluded, and the read fails gracefully with gambit_changes null plus a gambit_changes_error. It also discloses the api:read requirement and that reads never start a Gambit. What it doesn't do is state ordering/pagination stability beyond cursor and limit.

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?

A single block of ~450 words with no paragraphs, lists or headers; the core purpose and the routing hint are stated first but then buried under dense glossary-style digressions about Gambit semantics, versioning and judgment fields that belong in get_gambit or get_gambit_history. Many clauses (e.g. "A Gambit records that YOU follow an asset, with your own note; it has no stance of its own") do not help an agent invoke this tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description must describe returns and it does — field lists per kind, the gambit_changes shape, the nullable error field and app_url. That is thorough, but the tool is simple (three optional params) and the description's bulk is domain ontology rather than invocation essentials, and some referenced fields (next_cursor vs cursor param) require the agent to bridge naming itself.

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

Parameters3/5

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

Schema coverage is 67% and both limit (1-100, default 20) and next_cursor are already in the schema. The description adds real meaning for include_gambit_changes — what qualifies as a live Gambit, that only followed tickers are included, and why you'd want it — plus the failure mode. But the added value is concentrated in one parameter while limit/cursor get only incidental restatement.

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?

Opens with a specific verb+resource and scope: "What changed across ALL of YOUR Gambits, newest first". It distinguishes itself from get_gambit/list_gambits by explaining what a Gambit is and how judgment differs from gambit_changes, but the purpose sentence is buried under a long ontology of item kinds rather than stated crisply up front.

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 names the use case ("the call for 'what changed on my Gambits'") and explains when include_gambit_changes applies, when first_look items should not be called new, and that app reads of a Gambit can mark_seen. It gives no explicit when-not-to-use routing to get_gambit_history or get_portfolio_updates, so an agent must infer the boundary.

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