Skip to main content
Glama
Sign In

Stock Compass

by io.github.Stock-Compass
OverviewDiscussionsAdmin

Trades

get_trades
Read-only

Recorded buys and sells, newest first. fees is what the broker charged, when the user gave it (fees_source provided); otherwise fees is null and estimated_fees is the estimate from the user's own trading-cost settings, as their P&L counts it.

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

Input Schema

NameRequiredDescriptionDefault
toNoTraded on or before, YYYY-MM-DD.
fromNoTraded on or after, YYYY-MM-DD.
limitNoDefault 100.
marketNohk = Hong Kong, us = United States, cn = China A-shares.
offsetNoDefault 0.
tickerNoFor example 0700.HK or 700 (hk), AAPL (us), 600519.SS or 600519 (cn).
external_idNoOnly the trade recorded with this external_id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior4/5

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

The annotations already establish that this is a safe read-only operation. The description adds useful behavioral context beyond annotations by disclosing the default newest-first ordering and explaining the provenance of fees versus estimated_fees, including the role of fees_source and the user's trading-cost settings.

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

Conciseness4/5

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

The description is short and front-loads the key retrieval behavior with 'Recorded buys and sells, newest first.' The second sentence is dense but earns its place by explaining fee return semantics that are not covered by the input schema or annotations.

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 input schema richly documents all requested parameters, and annotations cover safety. However, with no output schema, the description only partially explains the returned trade shape by focusing on fees and estimated_fees while omitting other likely return fields and pagination behavior.

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 all seven input parameters are fully documented in the schema itself. The description does not add any parameter-level meaning beyond that, but it does not need to compensate for gaps.

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 clearly identifies the resource as recorded trades and states the default ordering, newest first. It is specific enough to distinguish this from trade mutation siblings like record_trade, edit_trade, and delete_trade, though it does not explicitly name those alternatives.

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?

The description gives no explicit guidance on when to use this tool versus related siblings such as record_trade, edit_trade, or delete_trade. Usage is only implied by the phrase 'Recorded buys and sells,' with no exclusions or routing advice.

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

All Stock Compass toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources