Skip to main content
Glama

welcome

by com.thebalancedinvestorclub

list_my_trades

Read-onlyIdempotent

Your trades from the Trading Journal at The Balanced Investor Club. Optionally filter by status or ticker. Set include_notes to read back the thesis and lesson you wrote on each trade. Your data, your patterns — never advice.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoTrades to return; default 20
statusNoFilter by trade status
tickerNoFilter to a specific ticker
include_notesNoInclude the thesis, exit reason, lesson and notes written on each trade. Off by default because they are long — turn it on when looking at a handful of trades, not a whole book.
include_paperNoInclude paper/practice trades, which are excluded from your stats. Off by default, matching the journal on the site.

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the safety profile is covered. The description adds the note that include_notes is off by default because notes are long, which is useful behavioral context, but does not disclose side effects or auth requirements beyond what annotations imply.

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 three sentences, front-loaded with the resource, and gets directly to filters and notes without wasted words.

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?

For a read-only list tool, the description covers its purpose, filters, and the special note option, which is sufficient for basic use. It lacks explicit mention of pagination or output structure, but those are not expected with no output schema and are partially handled by the parameter descriptions.

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%, so all five parameters already have descriptions. The description repeats filter options and explains the purpose of include_notes, but does not add meaning beyond the schema's detailed 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?

The description clearly identifies the tool as listing the user's trades from the Trading Journal, with optional filters by status or ticker. It distinguishes itself from siblings by referencing 'your trades' and 'read back the thesis and lesson,' which is specific to this journal tool, not other instrument or watchlist tools.

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 description implies usage for viewing one's trades and provides guidance on optional filters and include_notes. However, it does not explicitly name alternatives or when not to use this tool, though the context is clear enough given the sibling set.

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

All welcome toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.9/5.0
Disambiguation4/5

With 57 tools, most have distinct purposes (market data, journaling, watchlists). A few related tools (get_price_alignment vs get_crypto_price_alignment, get_market_pulse vs get_market_movers) could cause miselection, but descriptions clarify asset types and scope.

Naming Consistency4/5

Tools predominantly use get_/list_/create_/update_/delete_ verbs with clear noun suffixes. Minor deviations like start_here, whoami, add_to_watchlist, and remove_from_watchlist break the pure verb_noun pattern, but the style is consistent and readable.

Tool Count1/5

At 57 tools, the server is far beyond the well-scoped range. While the domain is broad, this many tools will overwhelm an agent's capability to select accurately, and many could be consolidated (e.g., separate financial statements).

Completeness5/5

The server covers watchlist CRUD, trading journaling, market data (fundamentals, statements, news, transcripts), analysis tools, and community features. No obvious dead ends; lifecycle coverage is thorough for the described domain.

Resources