Skip to main content
Glama

Export My Reports

tt_export_reports

Bundle the user's own trading data for a date range into a zip of CSVs and return a download link (strategies, day-by-day P&L, and every position with its broker fill).

THIS IS THE ESCAPE HATCH, NOT THE DEFAULT. If the user asks a QUESTION about their performance — "how am I doing?", "which strategy is losing money?", "what's my win rate?" — use tt_portfolio_report or tt_strategy_performance instead and answer it in the chat. Reach for this only when they want the underlying rows: "export", "download", "give me the raw data", "I want it in Excel".

Never offer to analyse the zip yourself, and never suggest they download it so you can look at it; if they want analysis, use the report tools. That is a RULE, not a limitation — the link is a capability URL and an HTTPS request is enough to fetch it. Follow the rule anyway.

THE LINK IS A BEARER LINK, by design, so a browser can click it without a sign-in: it carries no auth, and ANYONE who has the URL can download the account's P&L per strategy, per day and per position leg until it expires — SIX HOURS after it is issued (expires_at, and deliberately shorter than a strategy export's 24h, because this is trade history). Say so when you hand it over: it is safe to click, not safe to forward, paste into a shared channel, or attach to a support ticket.

Args: from_date: start of the window, YYYY-MM-DD. to_date: end of the window, YYYY-MM-DD. Max range is one year.

Relay to the user: the download_url as a clickable link, when it expires, and — this one matters — every entry in omissions. Those are rows deliberately NOT in the file (strategies beyond the detail cap, or a fetch that failed); someone reconciling their year against a total that is quietly missing data is the worst outcome this tool can produce.

Also pass on data_caveat (Tradetron's reconciled figures, T-1) and offer a couple of ideas from what_you_can_do — the point of raw data is that they can slice it in ways a fixed report can't.

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

Input Schema

NameRequiredDescriptionDefault
to_dateYes
from_dateYes

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?

Goes well beyond the annotations: the link is a bearer link with no auth, anyone holding the URL can download the account's data, it expires in six hours (shorter than a strategy export's 24h, with the reason given), and it returns an auth funnel when no account is connected. The annotations only mark it non-read-only, open-world and non-idempotent, so this detail is genuinely additive.

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, then usage routing, then security caveats, then argument format, then relay instructions — a sensible order. It is long, and the anti-analysis rule is restated twice ('Never offer to analyse the zip yourself' and 'Follow the rule anyway'), which costs some efficiency even though the emphasis is defensible.

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 fully by naming the return fields it cares about — download_url, expires_at, omissions, data_caveat, what_you_can_do — and by instructing the agent to surface omissions specifically. Nothing needed to call it or relay the result 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 0% — the schema has bare titles only — so the description must carry the load, and it does: from_date is the start of the window in YYYY-MM-DD, to_date the end in YYYY-MM-DD, with a stated maximum range of one year. That is enough to call the tool correctly without opening the schema.

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: bundle the user's own trading data for a date range into a zip of CSVs and return a download link, and enumerates the contents (strategies, day-by-day P&L, every position with broker fill). This is unmistakably distinct from the sibling analysis tools.

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?

Explicitly frames the tool as an escape hatch rather than the default, names the two alternatives (tt_portfolio_report, tt_strategy_performance) and the condition selecting them, and gives concrete user phrasings for each path ('how am I doing?' vs 'export', 'give me the raw data'). It also states the exclusion rule about not analyzing the zip oneself.

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