Skip to main content
Glama
lj22503

InvestBrain

by lj22503
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

broker_get_trade_stats

Aggregate imported trade statistics by date range and broker, including buy/sell counts, shares, amounts, fees, and distinct symbols. Use it to review trading activity and portfolio holdings.

Instructions

汇总已导入交易的统计指标（买卖笔数/股数/金额、费用、持仓标的数）。

Args:
    start_date: 起始日期 YYYY-MM-DD（含）
    end_date: 结束日期 YYYY-MM-DD（含）
    broker: 券商标识筛选（默认全部）

Returns:
    {buy: {...}, sell: {...}, total_trades, distinct_symbols, first_date, last_date}

Input Schema

NameRequiredDescriptionDefault
brokerNo
end_dateNo
start_dateNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations provided, the description carries the full behavioral burden. It discloses the data source ('已导入交易') and a partial return shape, and the aggregation nature strongly implies a read-only operation, but it does not explicitly state read-only safety, permissions, error behavior, or rate limits.

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 front-loaded with the tool purpose, then structured into Args and Returns sections. Every line contributes useful information with no redundancy or filler.

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 3-parameter statistics tool with no output schema, the description supplies the missing parameter details and a useful return-key summary. It is nearly complete, missing only explicit usage guidance against alternatives and read-only safety confirmation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate, and it does: it documents all three parameters, including date format (YYYY-MM-DD), inclusive bounds for start_date and end_date, and broker as an optional filter defaulting to all.

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 verb, '汇总' (aggregate), and a specific resource, '已导入交易' (imported trades), then lists the exact metrics computed. It clearly distinguishes this as a statistics tool rather than a listing or import tool, though it does not explicitly name sibling 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 implies the tool is for summarizing imported trades, but gives no explicit when-to-use guidance, no prerequisites, and no comparison to alternatives such as broker_list_trades or broker_get_imports. It leaves the agent to infer its place among siblings.

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