Skip to main content
Glama

Set position tracking

set_position_tracking
DestructiveIdempotent

Change Track all positions for YOUR account (requires api:account). Exactly one mode. track_all (true | false): turn the standing toggle on or off; on opens a Gambit on every held, trackable position that has none (up to the cap of 50) and answers the counts in sync (created, already_tracked, excluded, untrackable, capped), or sync null while automatic opening is switched off server-side; off stops nothing — the Gambits it opened stay. subject_id with tracked: true adds one position (it must be held; opens its Gambit or restores an archived one; 409 position_tracking_cap with cap at the limit; 404 position_not_held; 422 position_not_trackable when Hyperliquid does not list it); tracked: false removes it: every live Gambit on the asset is archived (restorable for 3 days with restore_gambit) and Track all positions never re-adds it until you add it again. Take subject_id from get_position_tracking. Confirm with the user before removing a position's Gambit. This places no order.

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": "set_position_tracking"
  }
}

Input Schema

NameRequiredDescriptionDefault
trackedNowith subject_id: true adds it, false removes it (archives its Gambit)
track_allNoturn Track all positions on (true) or off (false); not with subject_id
subject_idNoa held asset's subject_id from get_position_tracking, e.g. asset:equity:AAPL; with tracked

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?

Beyond the annotations, the description discloses caps, returned counts, null sync behavior, that turning tracking off does not stop existing Gambits, that removal archives live Gambits restorably for 3 days, and specific error cases such as 409 position_tracking_cap, 404 position_not_held, and 422 position_not_trackable. It also warns to confirm with the user before removing a position's Gambit and notes that no order is placed.

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?

The description is front-loaded with the core action and mode constraint, and most details earn their place given the tool's complexity. It is dense and packed into one paragraph with nested parentheticals, so it could be structured more cleanly, but it is not padded with irrelevant 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?

For a destructive, multi-mode tool with no output schema, the description covers the required permission, mode selection, side effects, caps, error outcomes, restoration path, confirmation guidance, and the fact that no order is placed. This is enough for an agent to invoke it safely and correctly.

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?

Although schema coverage is 100%, the description adds substantial meaning beyond field-level definitions: it explains the mutual mode constraint, the consequences of tracked true versus false, the requirement that subject_id refer to a held position, and what happens to the associated Gambit in each case.

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?

The description states a specific verb and resource: changing Track all positions for the account. It distinguishes the two operating modes, track_all and subject_id with tracked, and names get_position_tracking as the source of subject_id, so an agent can distinguish it from related tools.

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?

The description explicitly says 'Exactly one mode' and explains when to use track_all versus subject_id with tracked. It also tells the agent to take subject_id from get_position_tracking, confirms removal behavior, and directs restoration through restore_gambit after archiving.

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