ashare-screener
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ASHARE_DB | No | Optional path to the SQLite database file. Defaults to ./data/ashare.db | |
| TUSHARE_TOKEN | No | Tushare API token. Required for full market scan (run_screen full); not needed for test/pool modes or real-time quotes. Register free at https://tushare.pro |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| run_screenA | 跑完整5层漏斗选股(主板/换手/MA5/5年新高/筹码峰)。 mode: full=全市场(2-5分钟, 需 TUSHARE_TOKEN) | pool=自选池 | test=小样本(10支) |
| latest_resultsA | 查最近一次选股结果(读DB秒回,演示首选)。空库时友好提示。 |
| quoteB | 实时报价。ts_code 格式: 600519.SH / 000858.SZ |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
run_screen executes the funnel, latest_results reads stored output, and quote fetches live prices — three clearly distinct actions on distinct targets. No overlap or plausible misselection between them.
All names use lowercase snake_case, which is consistent. However, only run_screen follows a strict verb_noun pattern; latest_results and quote are noun-only, a minor deviation rather than a break in convention.
Three tools is slightly thin for a screener but each earns its place: execute, retrieve results, and live quotes. No redundancy, though one more tool (e.g. parameterized/custom screen) would round it out.
The core loop of run-screen → view-results → quote is covered, but there is no way to customize screen criteria, browse historical runs, or look up stock metadata beyond the quote call. These are notable gaps an agent may need to work around.