Skip to main content
Glama

My Deployed Strategies

tt_get_my_deployed_strategies
Read-onlyIdempotent

The signed-in user's DEPLOYED strategies and each one's status (Active, Live-Entered, Live-Tranching, Paused, Blocked, Error-Execution, Exit-Pending, Exited, ...) + mode (live / Live Offline).

Live-Entered is in a position; Live-Tranching is the transient state while a multi-tranche entry is being placed, and only matters when a deployment STAYS in it. Treat the value set as open-ended and compare case-insensitively.

q filters on the strategy NAME (case-insensitive substring) — use it when the user names one, rather than pulling the whole book to find it. limit/offset page the rows: the first 50 by default, with has_more / next_offset when there are more. total is the count after the filter and before paging; total_unfiltered is how many deployments the account has, so an empty filtered result is never mistaken for an empty account.

AUTH-REQUIRED (returns the connect/sign-up funnel if not authenticated). Use for "what have I deployed?", "which of my strategies are running / stopped?". To explain WHY one is in a given state, follow up with tt_get_my_deployed_strategy_detail using its strategy_id.

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

Input Schema

NameRequiredDescriptionDefault
qNo
limitNoRows to return, 1 or more. Default 50; page on with offset. 0 is refused.
offsetNoRows to skip. Default 0.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

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 AUTH-REQUIRED behavior and that unauthenticated callers get the connect/sign-up funnel. It explains paging defaults, has_more and next_offset, and the distinction between total and total_unfiltered. It also warns that the status value set is open-ended and should be compared case-insensitively.

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 purpose and then moves through status semantics, paging, auth, and usage examples. It is somewhat long and dense, but most sentences carry actionable information. Minor tightening of the status list and paging details would improve it.

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 annotations only cover safety hints, so the description carries the full burden. It supplies return-field meaning, paging behavior, filtered-vs-unfiltered counts, auth requirements, and the follow-up path to the detail tool. Nothing essential for calling this tool 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?

The schema leaves q undocumented, but the description explains that q filters on strategy NAME via case-insensitive substring. It also clarifies that limit and offset page rows, with 50 rows by default, adding meaning beyond the schema descriptions for limit and offset. This fully compensates for the 67% schema coverage.

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 resource, the signed-in user's deployed strategies, and the returned fields, status and mode. It distinguishes itself from the detail sibling by saying to use tt_get_my_deployed_strategy_detail for the WHY behind a state. An agent can identify the tool without opening the schema.

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?

It gives explicit user questions this answers, such as 'what have I deployed?' and 'which of my strategies are running / stopped?'. It also names the detail tool as the follow-up when the user needs an explanation, and instructs using q when the user names a strategy rather than pulling the whole book.

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