Skip to main content
Glama

Open a Gambit from a symbol

create_gambit
Idempotent

Open one of YOUR Gambits on a symbol, with an optional sentence in the user's own words (requires api:account) — the call for "start tracking GOOGL" or "watch whether HYPE holds its ETF bid". symbol is a bare ticker (BTC, GOOGL) or an exact Hyperliquid id (xyz:GOOGL for a HIP-3 market); search_symbols helps find it. A bare ticker listed on several HIP-3 markets (AVGO) is accepted when every listing is the same asset; the Gambit then uses that asset's main market (the xyz: listing for a stock), and other tickers that stay ambiguous need an exact id. sentence (up to 280 characters, the user's own words) is saved as the Gambit's note; it is never Gambit's view. If you already have an open Gambit on the same asset, the call returns that one instead of a second: created false and already_existed true. A returned Gambit is not changed: if its monitoring_status is paused (the user stopped it), tell the user and, only if they want it back, call update_gambit_monitoring with active=true. Known limit: Track in the Gambit app does not join a Gambit opened here, so tracking a card on the same symbol in the app can give the user a second Gambit on it; the next create_gambit on that symbol then answers gambit_choice_required and asks which one. A new Gambit records that the user follows the asset: it has no stance, no conviction and no direction, and nothing assesses the Gambit itself. Gambit's view of the asset is its shared take: read it with get_gambit (by case_id it is the gambit block; by symbol it is the view, and a ticker with no view yet answers status building). Returns case_id (pass it to get_gambit), created, already_existed, monitoring_status, and case (the Gambit in full, as get_gambit returns it). Errors (nothing is created on any of them): 422 code unknown_symbol, ambiguous_symbol with candidates (call again with one exact id), unsupported_symbol, invalid_sentence; 409 code gambit_choice_required with choices [{case_id, title}] when more than one open Gambit already tracks the asset (ask the user which one), or gambit_create_conflict (retry once); 429 gambit_create_limit after 10 creates in an hour; 503 when the symbol registry or the creation limit cannot be read (retry later). This places no order. The response carries app_url, the Gambit's screen.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "symbol": "<symbol>"
    },
    "name": "create_gambit"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolYesa ticker such as GOOGL or BTC, or an exact id such as xyz:GOOGL
sentenceNothe user's own words, saved as the Gambit's note; never Gambit's view

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / sentence / description
      Previous value: -"what to watch, in the user's words; becomes the monitoring question"New value: +"the user's own words, saved as the Gambit's note; never Gambit's view"
  2. Added

TDQS

A4.8/5.0
Behavior5/5

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

Goes well beyond the annotations (readOnly=false, idempotent=true, destructive=false) by spelling out what idempotency concretely means: an existing open Gambit on the same asset is returned with created=false and already_existed=true and is not modified. It adds rate limits (10 creates/hour, 429), a known divergence with the app's Track feature, the no-order side effect, and a per-error guarantee that nothing is created.

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 key action and scope are front-loaded, but everything after the first sentence is a dense, unbroken run-on paragraph mixing schema and error codes. Some content is redundant — "(the user's own words)" appears twice and the 280-character limit and note behavior are already in the schema — which costs the reader without adding information.

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, and the description covers the return payload (case_id, created, already_existed, monitoring_status, case, app_url) as well as the full error taxonomy. For an open-world-ish creation call with ambiguity and conflict states, nothing an agent needs in order to call it or recover from failure is missing.

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 real meaning: the ticker-vs-exact-Hyperliquid-id distinction (xyz:GOOGL for HIP-3), the ambiguity resolution rule for bare tickers listed on several markets, and 422 unknown_symbol/ambiguous_symbol/unsupported_symbol modes. For sentence it clarifies the note semantics and that it is never Gambit's view.

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?

States a specific verb and resource ("Open one of YOUR Gambits on a symbol") plus the user intents it serves ("start tracking GOOGL", "watch whether HYPE holds its ETF bid"). It also explicitly distinguishes itself from plan_gambit, get_gambit, update_gambit_monitoring and add_gambit_evidence by defining the Gambit as stance-less and pointing to get_gambit for views.

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?

Gives positive triggers, the prerequisite (api:account), the helper to call first (search_symbols for the ticker/id), and the follow-up for a paused result (update_gambit_monitoring with active=true, only if the user wants it). It also prescribes the exact recovery path for each error, e.g. re-calling with a candidate id on ambiguous_symbol and asking the user on gambit_choice_required.

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