Skip to main content
Glama

LogToLast Trading Journal & Playbook

Inspect Trade Execution by ID

inspect_trade_by_id
Read-onlyIdempotent

Fetches full execution telemetry, entry/exit timestamps, commission fees, trader notes, setup tags, and Playbook compliance details for a specific Trade ID. Set include_screenshots=true only when the user explicitly asks to inspect the saved chart images.

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": {
      "trade_id": "<trade_id>"
    },
    "name": "inspect_trade_by_id"
  }
}

Input Schema

NameRequiredDescriptionDefault
trade_idYesNumeric LogToLast Trade ID (from get_trading_summary_and_playbook).
include_screenshotsNoAttach up to 4 saved WebP chart screenshots when explicitly requested for visual analysis.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so safety is covered. The description adds value beyond them by enumerating the returned payload (telemetry, fees, notes, compliance details) and by flagging that screenshots are opt-in attachments limited to saved images, which implies a size/latency cost the agent should avoid triggering casually.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, zero filler: the payload enumeration is front-loaded and the conditional caveat follows it. Every clause carries information an agent needs.

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 correctly compensates by listing the returned fields, and annotations cover the safety profile. It is only slightly short of complete because it says nothing about behavior for a nonexistent or unauthorized trade_id.

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 description coverage is 100%, so both trade_id and include_screenshots are already fully documented in structured form. The description reinforces the include_screenshots opt-in constraint but adds no new syntax, format, or edge-case meaning, so the baseline 3 applies.

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?

The description opens with a specific verb ('Fetches') and an enumerated resource set (execution telemetry, timestamps, commissions, notes, tags, Playbook compliance) scoped to a single Trade ID, so the agent knows exactly what comes back. It doesn't explicitly name get_trading_summary_and_playbook as the alternative, but 'for a specific Trade ID' implicitly separates it from a summary-style tool.

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?

The second sentence gives an explicit conditional rule for the optional parameter ('Set include_screenshots=true only when the user explicitly asks'), which is real when-to guidance including an exclusion. There is no statement about when to prefer this tool over the summary sibling or what to do if the ID is unknown, so it stops short of full routing guidance.

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