Skip to main content
Glama

LogToLast Trading Journal & Playbook

Get Trading Summary & Playbook

get_trading_summary_and_playbook
Read-onlyIdempotent

Fetches the trader's quantitative performance metrics (win rate, profit factor, net PnL, expectancy), persistent Core Memory profile, active Playbook rules, and recent Master Account executions (excluding internal consolidated/duplicate copier follower rows).

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": "get_trading_summary_and_playbook"
  }
}

Input Schema

NameRequiredDescriptionDefault
lookback_tradesNoMaximum number of recent closed executions to include in the log (1-60). Defaults to 60.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, closed-world, and non-destructive, so the safety profile is covered. The description adds genuinely useful data semantics, notably that internal consolidated/duplicate copier follower rows are excluded from executions. It stops short of saying whether metrics are computed over the lookback window or over all history, which is a meaningful ambiguity.

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?

A single dense sentence that front-loads the verb and lists the returned artifacts in a scannable order. No filler, though the parenthetical exclusion interrupts the sentence flow and could be trimmed or restructured.

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 carries the burden of describing return content and does so thoroughly by enumerating the four result categories. The remaining gap is the ambiguous relationship between the lookback window and the computed metrics.

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 the single parameter is fully documented with bounds and default, so the schema does the work. The description adds no meaning about lookback_trades or whether it scopes only the execution log or also the metrics.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Specific verb ("Fetches") plus an explicit enumeration of the four resources returned: performance metrics, Core Memory profile, Playbook rules, and recent executions. It clearly differs from a single-trade lookup sibling, though it never names or contrasts with it.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

The description gives no when-to-use or when-not-to-use guidance and no mention of the alternative (inspect_trade_by_id) for drilling into individual trades. The agent must infer that this is the broad orientation tool based on the output list alone.

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