Skip to main content
Glama

Get position tracking

get_position_tracking
Read-onlyIdempotent

YOUR positions and whether each is tracked as a Gambit (requires api:portfolio) — Track all positions. Returns track_all (the standing toggle: while on, Gambit opens a Gambit on every position you hold, new ones included), sync_enabled (false while automatic opening is switched off server-side), cap (the most open Gambits that positions may hold, 50), open_position_cases (how many are open now), positions_read_at (when Gambit last read your holdings; null until the first read, which follows this call within about a minute — then call again; reading keeps them refreshed for 24 hours), and positions: one row per asset you hold, across every Hyperliquid wallet and every linked brokerage, as Gambit last read them (a position not refreshed for 6 hours is left out). Each row: subject_id (pass it to set_position_tracking), ticker, instrument_id (the Hyperliquid listing; null when not listed), sources (hyperliquid | brokerage), holdings (source, quantity — signed, negative is short —, instrument_kind, as_of), case_id and case_state (its Gambit, live or archived; null when none), tracked (a live Gambit follows it), excluded (you removed it, or archived its Gambit: Track all positions leaves it alone) and trackable (false when Hyperliquid does not list the ticker: it cannot be tracked, which is not an error). A position that closes keeps its Gambit. Read-only.

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_position_tracking"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description layers substantial extra behavior on top: the api:portfolio requirement, the 24-hour refresh window, the 6-hour staleness exclusion, and the 50-Gambit cap. It also pre-empts a likely failure mode by saying an untrackable ticker is not an error.

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 dense block of stacked parentheticals and mid-sentence dashes that is hard to parse on first read. Almost every clause carries information, but the return-field inventory would be clearer as structure than as prose.

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?

With no output schema and no parameters, the description carries the full burden of explaining returns, and it does so exhaustively: top-level fields, per-row field meanings, null conditions, and lifecycle behavior for closed positions. Nothing an agent needs in order to interpret the response 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?

The tool takes no parameters, so the baseline is 4; the schema is trivially complete. The description goes further by documenting the returned subject_id and its role as the input to set_position_tracking, which is useful downstream context rather than input semantics proper.

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?

"YOUR positions and whether each is tracked as a Gambit" gives a specific object plus the exact derived attribute, and the required scope (api:portfolio) is stated up front. An agent can separate this from get_holdings or set_position_tracking without consulting either 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 operational guidance: call again after about a minute when positions_read_at is null, and pass subject_id to set_position_tracking. It does not explicitly contrast with get_holdings, so an agent must infer which read tool to prefer for raw holdings versus tracking state.

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