Quant2Ptrader-MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| convert_joinquant_to_ptradeA | 将聚宽（JoinQuant）策略代码转换为Ptrade格式。可以直接输入代码字符串，或提供文件路径（支持.py/.txt等格式）。自动识别并转换所有API调用，生成Ptrade可用的.py文件和详细转换报告。 |
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 1 tool
With only one tool, there is no ambiguity or overlap with other tools. The tool has a single, clear purpose: converting JoinQuant strategy code to Ptrade format, making it impossible for an agent to misselect between tools.
The tool name 'convert_joinquant_to_ptrade' follows a consistent verb_noun pattern, using snake_case and clearly describing the action (convert) and target (JoinQuant to Ptrade). Since there is only one tool, consistency is inherently perfect.
A single tool is too few for a server named 'Quant2Ptrader-MCP', which suggests a broader scope for quantitative trading strategy conversion. While the tool is well-defined, the set lacks related operations like validation, testing, or reverse conversion, making it feel incomplete for the implied domain.
The tool surface is severely incomplete for the server's apparent purpose of converting between trading platforms. There are significant gaps, such as no tools for validating converted code, handling errors, or supporting other conversion directions (e.g., Ptrade to JoinQuant), which could lead to agent failures in real-world workflows.