Skip to main content
Glama
Sign In
MaverickMCP

MaverickMCP

by wshobson
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

journal_add_trade

Record an open trade with symbol, side, entry price, and shares. Optionally add rationale, tags, and notes for journaling.

Instructions

Add an open trade to the journal. Record the symbol, side (long/short), entry price, and number of shares. Optionally include a rationale, strategy tags, and notes. Entry date defaults to now.

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": {
      "symbol": "<symbol>",
      "side": "<side>",
      "entry_price": "<entry_price>",
      "shares": "<shares>"
    },
    "name": "journal_add_trade"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolYes
sideYes
entry_priceYes
sharesYes
rationaleNo
tagsNo
notesNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior2/5

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

No annotations are provided, so the description bears full responsibility for behavioral disclosure. It mentions default entry date to 'now' but does not explain validation, side effects, error handling, or return values. The output schema is not referenced.

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?

The description is extremely concise: two sentences. The first sentence clearly states the action and required parameters, and the second adds optional fields and a default behavior. No unnecessary words.

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?

Given the complexity (7 parameters, 0% coverage, no annotations, many siblings), the description is adequate but incomplete. It covers core functionality but lacks usage guidance, behavioral details, and output information. Context signals indicate a need for more depth.

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?

With 0% schema description coverage, the description should compensate. It lists the required and optional parameters and specifies that side is 'long/short', adding meaning beyond the schema. However, it does not explain formats for symbol, entry_price, or shares beyond their listing.

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?

The description clearly states the tool's purpose: 'Add an open trade to the journal.' It lists the required fields (symbol, side, entry price, shares) and optional ones, distinguishing it from siblings like journal_close_trade and journal_list_trades.

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

Usage Guidelines3/5

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

The description implies usage for recording new open trades but does not explicitly state when to use it versus alternatives (e.g., journal_close_trade). No when-not or alternative guidance is provided.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools