CLI for financial data management, local DuckDB database operations, and remote API integration with Fuyao API for A-share market data
This MCP server exposes a CLI tool wrapper with 36 tools, but lacks critical definition quality across the board. Tool names use inconsistent patterns (auth login vs data sync vs db query) without clear verb-noun structure. Most critically, NO input schemas are visible in the provided source code, only parameter names and descriptions are listed. Output schemas are completely undocumented. Descriptions exist but are minimal (10-50 chars typically), providing no guidance on WHEN to use each tool, what it returns, or how it chains with others. Error handling is not documented. The server is STDIO-only, which is a hard transport cap. No tool annotations (readOnlyHint, destructiveHint, idempotentHint) are present despite many tools being destructive (auth logout, data remove, skills remove). Parameter descriptions lack format constraints, ranges, or enum declarations, e.g., 'fileFormat' accepts 'ndjson, csv, or parquet' but is not declared as an enum. No evidence of pagination support for list tools. Security-critical tools (auth login) accept API keys as parameters, violating secret-injection pattern.
Store an API key in the system credential store
Delete API key credentials
Show whether an API key is configured
Show resolved non-secret configuration
Clean managed download cache
Initialize local data from a verified dump or remote Fuyao API
Plan or execute schema migrations
Delete database file
Rebuild derived factors (forward and backward adjustment factors)
NO input schemas visible in source code. All 36 tools list parameters but provide no JSON Schema definitions with types, constraints, or enums.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 39 | 2026-07-28+ | v2 |
Show local database status and schema compatibility
Synchronize local data from Fuyao API
Validate local data quality
Describe local database objects (list all tables and views)
Export a read-only SQL query result to file (ndjson, csv, or parquet)
Run a read-only SQL query against local DuckDB
Query balance sheet data from remote Fuyao API
Query cash flow statement data from remote Fuyao API
Query income statement data from remote Fuyao API
Query fund holder data from remote Fuyao API
Query fund performance data from remote Fuyao API
Query fund profile data from remote Fuyao API
Query futures market data from remote Fuyao API
Query index constituent stocks from remote Fuyao API
Query index quote data from remote Fuyao API
Query index valuation data from remote Fuyao API
Query market kline (candlestick) data from remote Fuyao API
Query market quote data from remote Fuyao API
Query options market data from remote Fuyao API
Remove CLI-managed Skills; --agent removes one target and excludes it from auto detection
Inspect bundled content, saved strategy, and each managed Agent target
Sync saved targets; --agent appends a target, and --agent auto enables detection
Query hot themes data from remote Fuyao API
Query top list data from remote Fuyao API
List all available securities from remote Fuyao API
Search for securities by code or name from remote Fuyao API
Query current A-share valuation snapshot from remote Fuyao API
Descriptions are minimal (10-50 chars) and lack LLM-critical context: WHEN to use each tool, what it returns, and how it chains with others. E.g., 'Query balance sheet data from remote Fuyao API' does not explain what parameters are required, what fields are returned, or when to call it vs income-statement.
Security violation: auth login accepts 'apiKey' as a parameter. Per pattern:secret-injection, credentials must NEVER appear as tool parameters, they leak into agent logs and traces. Use server-side secret injection via environment or vault instead.
No tool annotations (readOnlyHint, destructiveHint, idempotentHint) despite many destructive tools: auth logout, data remove, skills remove, data clean, data migrate. LLMs cannot distinguish safe from dangerous operations without explicit hints.
Parameter constraints not formalized. E.g., db export 'fileFormat' lists 'ndjson, csv, or parquet' in description but is not declared as an enum.