Skip to main content
Glama

Report Template

tt_report_template
Read-onlyIdempotent

Run a ready-made report over the user's own trading data and render it in the chat. Four templates, each answering a question that tt_portfolio_report (a ranked snapshot) and tt_strategy_performance (one strategy) do not:

  • "monthly" — month-by-month P&L across the whole book, with a running total, best/worst month, positive-month count. For "how has my year gone?", "show me my monthly P&L".

  • "by_underlying" — which instruments the money actually comes from, ranked, with each one's share. For "which stocks make me money?", "where am I losing?".

  • "execution" — average slippage with the worst fills listed, plus how many legs carry a broker execution record (Live Offline legs never do). Partial fills are NOT detectable from this feed. For "is slippage hurting me?".

  • "paper_vs_live" — the book split by mode, Live Offline beside live (not comparable on performance: Live Offline fills at LTP). For "how do my Live Offline and live results differ?".

Prefer these over tt_export_reports whenever the user is asking a QUESTION — this answers it in the conversation; the export just hands them a zip they have to open themselves.

Args: template: one of monthly | by_underlying | execution | paper_vs_live. from_date: YYYY-MM-DD. to_date: YYYY-MM-DD.

Follow the returned render_spec — it says how to lay the report out and, importantly, keeps the interpretation DESCRIPTIVE. Never turn these numbers into "stop this strategy" or "put more into that one": this is live money and that is investment advice. Describe what the data shows and let the user decide.

Always relay omissions (parts of the book not covered) and any method_caveat — a breakdown that quietly covers half the book reads as complete and is worse than none.

AUTH-REQUIRED: returns the connect funnel when no account is connected.

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": {
      "template": "<template>",
      "from_date": "<from_date>",
      "to_date": "<to_date>"
    },
    "name": "tt_report_template"
  }
}

Input Schema

NameRequiredDescriptionDefault
to_dateYesYYYY-MM-DD.
templateYesOne of: monthly, by_underlying, execution, paper_vs_live. Matched case-insensitively.
from_dateYesYYYY-MM-DD.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, and the description adds genuinely useful context beyond that: the render_spec contract, the DESCRIPTIVE-only interpretation constraint, the AUTH-REQUIRED connect funnel, and two concrete data limitations ('Partial fills are NOT detectable from this feed', Live Offline fills at LTP and is not comparable on performance).

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 one-line purpose, then a scannable per-template list each ending in example queries, then operational constraints. Slightly long, and the closing 'Args:' block largely restates the input schema, which is the only real waste; every other sentence carries behavioural or routing weight.

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, so the description carries the return-value burden itself and does: it names render_spec, omissions and method_caveat, and instructs the agent to relay the latter two. For a read-only reporting tool with three fully documented parameters, nothing an agent needs in order to call it and present results correctly 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 100%, so the baseline is 3, but the description exceeds it: the schema's template parameter has no enum, and the description is the only place the four values are defined with their semantics and selection heuristics. Date parameters only get the format restated, matching the schema, so it stops short of a 5.

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 ('Run a ready-made report over the user's own trading data and render it in the chat') and then enumerates all four templates with the question each answers. It explicitly names what tt_portfolio_report and tt_strategy_performance do not cover, so an agent can separate this tool from its nearest siblings without opening any 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 explicit routing rules: 'Prefer these over tt_export_reports whenever the user is asking a QUESTION' with the reason (answer in conversation vs. a zip the user must open). Each template carries example user phrasings ('how has my year gone?', 'where am I losing?'), so template selection is a lookup rather than an inference. No exclusions are left implicit.

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