Skip to main content
Glama
lj22503

InvestBrain

by lj22503
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

broker_import_statement

Import broker CSV statements, parse them into standardized trade records, and save to InvestBrain while automatically removing duplicates.

Instructions

导入券商交割单 CSV 文件，解析为标准化交易记录并入库（自动去重）。

Args:
    file_path: 券商导出的交割单/对账单 CSV 文件绝对路径
    broker: 券商标识，可选 htsc / citic / cms / gtja / generic；
            默认 auto 自动按表头特征识别（无法确定时按 generic 处理）

Returns:
    {
      import_id, broker, file_name,
      total_rows, imported_rows, duplicated_rows, skipped_rows,
      first_date, last_date, warnings, hint
    }
    重复导入同一文件时返回 imported_rows=0 并提示已存在。

Input Schema

NameRequiredDescriptionDefault
brokerNoauto
file_pathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses idempotent dedup behavior (re-importing the same file yields imported_rows=0 and a 'already exists' hint), auto broker detection with generic fallback, and a warnings/hint channel. It does not cover permissions, file-size limits, or error modes, so it stops short of a 5.

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 purpose sentence is front-loaded, and the Args/Returns sections are tightly organized with no filler. The return-field enumeration is justified because no output schema exists. Slightly verbose but every part earns its place.

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 two-parameter mutation tool with no annotations and no output schema, the description supplies both parameter semantics and the full return shape (import_id, row counts, date range, warnings, hint), which fills the output-schema gap. Minor omissions around permissions and failure behavior keep it from a 5.

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 coverage is 0% with two parameters, so the description must compensate, and it does: file_path is documented as an absolute path to the broker's exported statement, and broker is given the candidate identifiers (htsc / citic / cms / gtja / generic) plus the auto default and its header-based detection logic. This adds meaning well beyond the bare schema.

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+resource: importing broker statement CSVs, parsing them into standardized trade records, and persisting them. This is unambiguous and clearly distinct from read-only siblings like broker_get_imports or broker_list_trades. It does not explicitly name a sibling, but the action is unique enough that an agent can identify it.

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?

There is no explicit when-to-use or when-not-to-use guidance, and no alternatives are named. The description implies usage context by explaining that broker defaults to auto-detection from header features, so an agent can call it with only file_path. That is useful implied guidance but falls short of explicit routing.

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