Skip to main content
Glama

Strategy Notifications

tt_get_strategy_notifications
Read-onlyIdempotent

Read the ENGINE NOTIFICATION LOG for ONE of the signed-in user's strategies — the deepest source for "why is my strategy in error / why didn't it trade / what did the engine actually do?". Returns the raw per-SID engine messages (position entries/exits, status transitions, tracebacks, broker rejections, blocks) plus an extracted errors list (the human reason a deployment erred).

Goes deeper than tt_get_my_deployed_strategy_detail: that reads TT's summarised /ai state; THIS reads the engine's own debug stream. Reach for it when the detail view's events don't explain the error.

AUTH-REQUIRED and OWNERSHIP-GATED + fail-closed: before reading anything the SID is reverse-looked-up against the caller's account (must be their deployment OR a template they created). If it isn't theirs — or the ownership lookup itself fails — the tool REFUSES and reads nothing. Do not present this as a way to inspect arbitrary strategies.

strategy_id is the deployed strategy id (SID); if the user names a strategy, resolve the id via tt_get_my_deployed_strategies first. 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_notifications"
  }
}

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 readOnly/idempotent annotations, it discloses auth requirements, ownership reverse-lookup per SID, fail-closed refusal behavior when the lookup fails, and the exact payload shape (raw per-SID engine messages plus an extracted `errors` list). This is exactly the operational context annotations cannot carry.

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?

Well front-loaded — purpose, sibling distinction, auth gating, then parameters — with almost no wasted sentences. Slight redundancy from the emphasized 'AUTH-REQUIRED and OWNERSHIP-GATED + fail-closed' header followed by prose restating it, and a few capitalized phrases add noise.

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, yet the description names the return contents (raw engine messages: entries/exits, status transitions, tracebacks, broker rejections, blocks, plus an errors list) and the two parameters' constraints. Nothing material to correct invocation 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 50% because strategy_id has no schema description; the description compensates by defining it as the deployed strategy id (SID) and prescribing the lookup workflow when only a name is known. window_minutes is reinforced with default 60 and the 1440 clamp/refusal behavior.

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 concrete verb and resource: 'Read the ENGINE NOTIFICATION LOG for ONE of the signed-in user's strategies'. It explicitly contrasts itself with tt_get_my_deployed_strategy_detail ('that reads TT's summarised /ai state; THIS reads the engine's own debug stream'), so an agent can separate the two without opening schemas.

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 a triggering question ('why is my strategy in error / why didn't it trade'), an alternative to try first, and a negative rule ('Do not present this as a way to inspect arbitrary strategies'). It also routes id resolution through tt_get_my_deployed_strategies when the user names a strategy.

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