Skip to main content
Glama

Trade journal

get_journal
Read-only

The trade journal, newest opened first, as the journal page shows it: each position opened, its price and shares, and once closed the close price and the realized return; what triggered the buy (a strategy signal with its strategy, a price alert, manual, imported, other); the thesis; the stop and target planned at entry and in force now, with the stop changes; the close reason, whether the plan was followed, and the lesson.

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_journal"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoOpened on or before, YYYY-MM-DD.
tagNoA label the user gave trades, such as the system or the kind of signal behind them.
fromNoOpened on or after, YYYY-MM-DD.
limitNoPage size. Default 100.
marketNohk = Hong Kong, us = United States, cn = China A-shares.
offsetNoWhere the page starts; take next_offset from the previous answer. Default 0.
statusNoDefault all.
tickerNoFor example 0700.HK or 700 (hk), AAPL (us), 600519.SS or 600519 (cn).
triggerNo

Output Schema

NameRequiredDescriptionDefault
errorNo
limitNo
totalNo
offsetNo
entriesNo
warningsNo
next_offsetNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedOutput schema / properties / error / properties / reason
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / properties / warnings
      Added value: +{
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
  2. Changed2 schema fields changed
    • addedOutput schema / properties / entries / items / properties / stop_history / items / properties / source
      Added value: +{
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / entries / items / properties / target_history
      Added value: +{
      +  "items": {
      +    "properties": {
      +      "at": {
      +        "type": "string"
      +      },
      +      "from": {
      +        "type": [
      +          "number",
      +          "null"
      +        ]
      +      },
      +      "source": {
      +        "type": [
      +          "string",
      +          "null"
      +        ]
      +      },
      +      "to": {
      +        "type": [
      +          "number",
      +          "null"
      +        ]
      +      }
      +    },
      +    "required": [
      +      "at",
      +      "from",
      +      "to"
      +    ],
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
  3. Added

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds the ordering guarantee (newest opened first) and explains that stop/target shows both entry-plan and currently-in-force values, but it says nothing about pagination behavior or volume/size expectations.

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

Conciseness3/5

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

The ordering constraint is front-loaded, which is good, but the bulk of the text is a single sprawling semicolon list enumerating returned fields that the output schema already documents. It is dense rather than concise, and much of its length does not earn its place.

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

Completeness3/5

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

The tool is read-only with full annotations, a rich schema, and an output schema, so the burden is low. The description covers ordering and record composition, but omits the one thing an agent most needs: how this differs from sibling retrieval tools when choosing among them.

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 89% and every parameter already carries a description, including enum definitions and date patterns. The description mentions triggers, tags, and statuses conceptually but adds no filtering semantics or defaults beyond what the schema states.

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 states a specific resource (the trade journal) and establishes ordering (newest opened first) plus the shape of each entry. It does not distinguish this from the closely named sibling get_trades, so an agent cannot tell which to choose from the description alone.

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?

There is no guidance on when to use this versus get_trades or get_journal_stats, and no mention of how filters like status, trigger, or tag should drive selection. Usage must be inferred entirely from the name and schema.

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.