performance-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PERFORMANCE_TOKEN | No | 已登录账号的短期 API Token | |
| PERFORMANCE_BASE_URL | Yes | 绩效系统服务地址，例如 https://performance.example.com | |
| PERFORMANCE_PASSWORD | No | 登录密码；仅在未设置 Token 时使用 | |
| PERFORMANCE_USERNAME | No | 登录账号；仅在未设置 Token 时使用 |
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_periodsA | List available performance assessment periods for the logged-in user. |
| list_performance_evaluationsA | List the current user performance evaluations. Use list_periods first when a period ID is needed. |
| get_performance_evaluation_detailA | Get the complete detail for one performance evaluation, including tasks, scores, comments, and code/document summary. |
| save_performance_draftA | Save self-evaluation scores and comments as a draft using the evaluation scores endpoint. This tool never submits a final evaluation. |
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 4 tools
Each tool targets a distinct resource or action: periods, evaluations list, evaluation detail, and draft saving. Descriptions clearly differentiate them, with no overlapping purposes.
All tool names follow a consistent verb_noun pattern using snake_case: 'list_periods', 'list_performance_evaluations', 'get_performance_evaluation_detail', 'save_performance_draft'. The verb choice (list vs get) appropriately distinguishes collection from single item retrieval.
With 4 tools, the server covers basic viewing and drafting for performance evaluations, which is a reasonable minimal set. It does not feel overly thin or excessive for the stated purpose.
The toolset supports listing periods and evaluations, viewing details, and saving drafts, but critically lacks a tool to submit or finalize an evaluation. This is a notable gap that would prevent completing the core evaluation workflow.