Skip to main content
Glama

Portfolio Report

tt_portfolio_report
Read-onlyIdempotent

The signed-in user's WHOLE BOOK over a window — the "how am I doing overall / which strategies are sinking me?" dashboard. Returns total P&L, every strategy ranked by P&L, the winners-vs-losers split, each loser's share of the total loss, and how concentrated the drawdown is in the top few losers.

Present it as a dashboard and give a DESCRIPTIVE read — name where the loss concentrates and the winner/loser asymmetry; do NOT tell the user which strategies to stop or fund (investment advice). Offer to drill into any one with tt_strategy_performance or tt_diagnose_strategy. Data is T-1; P&L reconciled. AUTH-REQUIRED. from_date/to_date ISO (empty = current month).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "tt_portfolio_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
to_dateNoYYYY-MM-DD; omit for yesterday (the data is T-1).
from_dateNoYYYY-MM-DD; omit for the start of the current month.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare read-only, idempotent, non-destructive behavior, and the description adds genuinely new context: AUTH-REQUIRED, data is T-1, P&L is reconciled, and the intended presentation format with a caution against giving prescriptive advice. It also discloses what the response contains in enough detail to plan the answer.

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 scope and purpose, then behavior and presentation guidance. Most sentences earn their place, though the dashboard/presentation instructions could be tightened into fewer clauses without losing meaning.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description does the work of describing return contents in detail, so an agent knows what to expect. It leaves out whether the ranked strategy list is bounded or paginated for very large books, which is the remaining gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and both parameters already document ISO format and defaults, so the baseline is 3. The description only restates ISO with "empty = current month," which is imprecise for to_date, since the schema says an omitted to_date means yesterday, so it adds little and is slightly inconsistent.

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 at a specific scope: the signed-in user's WHOLE BOOK over a window, framed as an overall P&L dashboard. It enumerates the returned content (total P&L, ranked strategies, winners-vs-losers, loser share, drawdown concentration), which clearly separates it from per-strategy siblings.

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 use case in the user's own words ("how am I doing overall / which strategies are sinking me?"), names the drill-down alternatives tt_strategy_performance and tt_diagnose_strategy, and states a when-not boundary around investment advice.

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