Skip to main content
Glama

List my Gambits

list_gambits
Read-onlyIdempotent

YOUR Gambits (the API key's user): each situation you track in Gambit, with what Gambit is watching and what it last found. Each row: id (pass it as case_id to get_gambit / get_gambit_history), title, state (open | watching | executed | dismissed | invalidated | played_out | expired; archived with archived=true), instrument_id and participants (what the Gambit is about), direction / expression_kind / setup_family when it tracks one trade expression, monitoring_status (active | paused), update_categories (news, market_activity, assessment) and monitor_interval_minutes (what is watched and how often), monitor_last_checked_at and monitor_last_result (the newest monitoring pass: status no_change | material_change | degraded, with per-source coverage), latest_observation (the newest news item or post attributed to it, with why_now — attention, not verified evidence), note (the user's own words from when they opened or tracked it; null when none), take (Gambit's shared take of the Gambit's asset: subject_id, version, as_of and line, the take in one line; null when Gambit has no view of it, for example a prediction market), current_judgment (the newest log entry; null when there is none) and judgment_count (how many log entries exist), mandate_id / mandate_links (the saved Gambits it belongs to), opportunity_entry_count and opportunity_latest_entry_at (the market opportunities its history shows: captured ones and the shared cards of its tickers, one per detector, ticker and UTC day), and created_at / updated_at / last_evaluated_at, plus archived_at and purge_at (null unless the Gambit is archived). 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. archived=true lists only YOUR archived Gambits (archive_gambit), each purged for good at purge_at unless restored with restore_gambit; the default lists the others. Paginate with limit (1-100, default 100) and offset. 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": "list_gambits"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
offsetNo
archivedNotrue lists only archived Gambits; default false

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / archived
      Added value: +{
      +  "description": "true lists only archived Gambits; default false",
      +  "type": "boolean"
      +}
  2. Added

TDQS

A4.5/5.0
Behavior5/5

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

Annotations cover the safety profile (readOnly, idempotent, non-destructive), and the description adds substantial behavior beyond that: the `api:read` scope requirement, the archived-vs-default listing partition, permanent purge at `purge_at` unless restored, pagination bounds and defaults, and that the response carries an `app_url`. It also flags real interpretive traps — `latest_observation` is 'attention, not verified evidence' and `why_now` is not proof.

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 purpose is front-loaded, but the body is one enormous run-on enumeration of every response field with semicolon-chained parentheticals, which is hard to scan. With no output schema the field detail is arguably load-bearing, yet it is presented as prose rather than a structured list, so density substitutes for structure.

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 3-param read tool with no output schema, the description covers the full contract: auth scope, pagination, archived lifecycle, every returned field with the caveats that matter (log-less Gambits from Nov 2026 on, prediction-market contracts, null `take`). Nothing an agent needs to call it correctly or interpret the result 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 only 33% (only `archived` is documented in-schema), so the description has to compensate, and it largely does: it explains the archived listing partition and its restore/purge lifecycle, and gives `limit` bounds (1-100, default 100) plus `offset`. `offset` paging mechanics (page-size interaction, termination) are left implicit, which keeps this short of a 5.

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?

Opens with a specific verb and scoped resource: 'YOUR Gambits (the API key's user)' plus the semantic payload ('each situation you track... with what Gambit is watching and what it last found'). It also explicitly routes the returned `id` to the siblings `get_gambit` / `get_gambit_history` as `case_id`, so an agent can distinguish list vs. detail without opening another schema.

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?

Gives concrete selection rules: default lists active Gambits, `archived=true` lists only your archived ones (with `archive_gambit` / `restore_gambit` named as the mutators), and pagination via `limit`/`offset`. It also tells the agent not to present the result as Gambit's own view. It stops short of stating when to prefer this over `list_mandates` or `get_my_opportunity_marks`, so it is clear context rather than full when/when-not guidance.

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