Skip to main content
Glama

Strategy Performance Report

tt_strategy_performance
Read-onlyIdempotent

How is ONE of the signed-in user's deployed strategies PERFORMING (the money question, distinct from tt_diagnose_strategy's "is it broken"). Returns total P&L over the window plus the daily series and the stats that matter: win-days vs loss-days, win-rate, avg win-day vs avg loss-day, payoff ratio, best/worst day, daily volatility, max drawdown, and volatility-vs-return. Keyed by the same SID as diagnosis, so you can say both "it's not broken" AND "but it's barely net-positive with huge daily swings".

Present the numbers, then give a DESCRIPTIVE read — quantify the behaviour; do NOT give buy/sell/allocation advice (that's investment advice on live money). Data is T-1; P&L is TT's reconciled figure.

AUTH-REQUIRED + ownership-gated. from_date/to_date are ISO dates (empty = TT's default current-month window).

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

Input Schema

NameRequiredDescriptionDefault
to_dateNo
from_dateNo
strategy_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the annotations (readOnly/idempotent/closed-world), it discloses authentication and ownership gating, T-1 data lag, that P&L is TT's reconciled figure, and that an empty date range falls back to a current-month default. It also states a compliance constraint on how to present results, which is real behavioral context an agent could not infer from structured fields.

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 purpose and the sibling contrast, then the return payload, then constraints. Some framing is chatty ('the money question', the rhetorical quote about barely net-positive) but each block does carry information.

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 description compensates by enumerating the returned metrics (P&L, daily series, win-rate, payoff ratio, max drawdown, volatility-vs-return). Combined with auth, data-freshness and default-window notes, an agent has enough to call it and to report results correctly.

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%, so the description carries the burden. It explains that from_date/to_date are ISO dates with empty meaning the default current-month window, and that strategy_id is 'the same SID as diagnosis' — most of what an agent needs. Residual gap is that no explicit example or range constraint is given for the dates.

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 opens with a specific verb+resource+scope: performance of ONE of the signed-in user's deployed strategies, and explicitly contrasts that with tt_diagnose_strategy's 'is it broken' framing. An agent can route between the two tools 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 Guidelines4/5

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

It names the closest alternative and states the distinguishing condition ('the money question' vs 'is it broken'), plus a clear boundary on what to do with the output (describe, don't advise). It does not address other siblings such as tt_portfolio_report, so the routing picture is clear but not exhaustive.

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