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 that says what to watch (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) becomes the Gambit's monitoring question; without it Gambit uses a general outlook question. 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 starts with a neutral watch judgment (stance watch, conviction low) and no direction; Gambit's monitor writes the first real assessment on its normal schedule, so read it later with get_gambit or get_tracking_updates. 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.

Input Schema

NameRequiredDescriptionDefault
symbolYesa ticker such as GOOGL or BTC, or an exact id such as xyz:GOOGL
sentenceNowhat to watch, in the user's words; becomes the monitoring question

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.9/5.0
Behavior5/5

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

Annotations only cover the safety/idempotency profile; the description goes far beyond by disclosing the auth requirement (api:account), the dedupe behavior (created=false, already_existed=true), the 10-per-hour rate limit, the initial neutral stance/conviction state, the 'no order placed' guarantee, and the full error taxonomy with codes and recovery actions. It is consistent with idempotentHint=true rather than contradicting it.

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?

Core action is front-loaded and every clause carries information, but the single dense paragraph stacks parentheticals and error codes, making it heavy to scan. It earns its length but could be structured into shorter sentences without losing content.

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?

Despite no output schema, the description enumerates the return fields (case_id, created, already_existed, monitoring_status, case, app_url) and explains the call's lifecycle, error states, and follow-up reads. Nothing an agent needs to invoke and interpret this correctly 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 still adds meaning the schema cannot: symbol resolution rules for bare tickers, exact Hyperliquid ids (xyz:GOOGL), and the ambiguity policy when a ticker lists on several HIP-3 markets, plus sentence's 280-char limit and its role as the monitoring question with a documented default when omitted.

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+resource ('Open one of YOUR Gambits on a symbol') with the scope ('on a symbol') and even maps real user utterances ('start tracking GOOGL') to the call. It distinguishes itself from siblings by naming get_gambit, update_gambit_monitoring, search_symbols and get_tracking_updates and explaining how each relates.

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?

Explicit when-to-use with example phrasings, when to reach for search_symbols (finding the symbol), and what to do when a Gambit already exists (returns it rather than creating a second; if paused, prompt the user before calling update_gambit_monitoring with active=true). It also tells the agent what to do on gambit_choice_required (ask the user) and on retryable errors.

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