Skip to main content
Glama
wshobson

MaverickMCP

journal_close_trade

Close an open trade by entry ID, provide exit price, and automatically compute PnL and update strategy performance metrics.

Instructions

Close an existing open trade by entry ID. Provide the exit price; exit date defaults to now. PnL is automatically computed (long: exit-entry, short: entry-exit). Strategy performance metrics are recomputed for all tags on this trade.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
entry_idYes
exit_priceYes
notesNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

Discloses exit date defaults to now, automatic PnL computation with clear formulas for long/short, and strategy performance recalc for all tags. No annotations exist, so description provides necessary behavioral context.

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, each conveying essential information: purpose/defaults and side effects. No redundancy.

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 output schema present, description adequately covers behavior and side effects. Could mention that entry_id must reference an open trade, but minimal gap given tool simplicity.

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 0%; description explains exit_price meaning and default for exit date, but does not describe entry_id or notes parameter. Adds PnL formula context but lacks full parameter descriptions.

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?

Clearly states the tool closes an open trade by entry ID, distinguishing it from siblings like journal_add_trade (adds a trade) and journal_list_trades (lists trades). The verb 'close' and resource 'trade' are specific.

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?

Implies usage is for closing open trades when exit price is available, but lacks explicit when-not-to-use or alternatives. No comparison with sibling tools like journal_trade_review.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/wshobson/maverick-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server