Skip to main content
Glama

Deployed Strategy Detail

tt_get_my_deployed_strategy_detail
Read-onlyIdempotent

Deep read on ONE of the signed-in user's deployed strategies — the tool for "why is my strategy in error / blocked / stuck?". Returns its current status, recent event log (the human-readable reason it halted or errored), the broker connection it trades through, and recent orders (a rejection carries the broker's reason). AUTH-REQUIRED.

strategy_id is the numeric id from tt_get_my_deployed_strategies — if the user names a strategy ("my abc strategy"), call that tool first to resolve the id, then call this. Reasoning over the returned status + events + orders is up to you; the data is scoped to the caller (another user's id returns not-found).

Two things the rows do not say themselves. recent_events is mostly Status Change entries — they record a state move, not what the strategy did, they name no order or condition, and several share one whole-second timestamp, so their returned order is arbitrary and will not always chain: read status for the current state, never the last event. And an order row with broker_order_id null carries no broker execution record at all — on a LIVE-OFFLINE deployment (no order is placed there) that is every row, and status "Initiated" with executed_quantity 0 is where they stop for good, not a stuck order. The response's orders_caveat and events_note carry both in full when they apply.

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": {
      "strategy_id": "<strategy_id>"
    },
    "name": "tt_get_my_deployed_strategy_detail"
  }
}

Input Schema

NameRequiredDescriptionDefault
strategy_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only cover safety (readOnly, idempotent, closed-world); the description then contributes auth requirement, per-caller scoping (another user's id returns not-found), and two subtle data caveats — Status Change events have arbitrary ordering at whole-second granularity and null broker_order_id rows on LIVE-OFFLINE deployments are terminal, not stuck.

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?

Front-loaded with purpose and the user question, then returns, then parameter resolution, then caveats — a sensible ordering. The caveat paragraph is dense but long and slightly repetitive with the note that `orders_caveat`/`events_note` restate it in the response.

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?

No output schema exists, and the description compensates fully by enumerating the returned sections (status, recent events, broker connection, recent orders) plus the caveat fields. Nothing needed to invoke or interpret the call 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?

Schema coverage is 0% and the schema says only 'Strategy Id', so the description has to carry the meaning — it does, specifying the id is numeric and comes from tt_get_my_deployed_strategies, plus the not-found behavior for foreign ids. It could still note whether a missing/invalid id errors vs returns empty.

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 ('Deep read on ONE of the signed-in user's deployed strategies') and pins the use case with a quoted user question ('why is my <name> strategy in error / blocked / stuck?'). It implicitly distinguishes itself from the plural list tool by emphasizing ONE strategy.

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?

Names the alternative explicitly: if the user names a strategy, call tt_get_my_deployed_strategies first to resolve the numeric id, then call this. It also states the diagnostic trigger condition and the auth prerequisite, leaving little to inference.

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