Skip to main content
Glama

Strategy Broker Log

tt_get_strategy_broker_log
Read-onlyIdempotent

Read the BROKER LOG (broker-adapter daemon) for ONE of the signed-in user's strategies — the layer BELOW the engine notification log. Where tt_get_strategy_notifications shows what the engine decided, this shows what the BROKER actually did: order placement, the broker API request/response, order-status polling (OPEN/COMPLETE/REJECTED), modify/retry loops, and broker-side failures (RMS / margin / token / auth rejections). Use it when a strategy errored but the engine log is clean — the failure is usually at the broker.

Returns the raw broker lines plus extracted broker_hosts, orders placed ({symbol, price}), distinct order_statuses, and the ERROR/rejection lines (the broker-side reason).

AUTH-REQUIRED and OWNERSHIP-GATED + fail-closed, identical to tt_get_strategy_notifications: the SID is reverse-looked-up against the caller's account first; not theirs (or an inconclusive lookup) ⇒ REFUSE.

strategy_id is the deployed strategy id (SID); resolve via tt_get_my_deployed_strategies if the user names a strategy. window_minutes is the lookback (default 60, max 1440).

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

Input Schema

NameRequiredDescriptionDefault
strategy_idYes
window_minutesNoLog lookback in minutes, 1..1440. Default 60. A larger value is clamped to 1440; below the minimum is refused.

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 readOnly/idempotent/non-destructive annotations, the description discloses that the call is AUTH-REQUIRED and OWNERSHIP-GATED with fail-closed behavior, that the SID is reverse-looked-up against the caller's account, and that an inconclusive lookup results in a REFUSE. It also enumerates the payload (raw broker lines, broker_hosts, placed orders, order_statuses, ERROR/rejection lines), which is meaningful since there is no output schema.

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 the core statement and organized into purpose, contrast, use-case, return payload, and auth semantics. Slightly dense with all-caps emphasis and backtick formatting, but no sentence is filler; the extra length is carrying real disclosure burden left by the missing output schema.

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 2-parameter read tool with no output schema, the definition covers purpose, alternative routing, auth/ownership failure modes, parameter resolution, and returned fields. Nothing an agent needs to call it correctly or interpret the refusal path 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 only 50%, and the description compensates fully: it explains that strategy_id is the deployed strategy id (SID) and how to resolve it, and that window_minutes is the lookback with default 60 and max 1440, including clamping and refusal behavior. This adds meaning beyond the schema for the undocumented required parameter.

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 ("Read the BROKER LOG ... for ONE of the signed-in user's strategies") and explicitly positions it as "the layer BELOW the engine notification log," naming the sibling tt_get_strategy_notifications as the contrasting tool. An agent can distinguish decided vs. did without opening 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 Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit when-to-use rule: "Use it when a strategy errored but the engine log is clean — the failure is usually at the broker." It also names the alternative (tt_get_strategy_notifications) and the condition that selects it, plus a routing hint to tt_get_my_deployed_strategies when the user names a strategy rather than a SID.

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