Appraisal Tracker MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DEFAULT_LEVEL | Yes | Your appraisal level (e.g., lead_consultant, senior_consultant, principal_consultant) | |
| TRACKER_FOLDER | Yes | The subfolder inside the vault where all tracker files will be created | |
| OBSIDIAN_VAULT_PATH | Yes | The root folder of your Obsidian vault (or any folder where you want the notes saved) |
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 |
|---|---|
| get_appraisalB | Get all appraisal goals for a specific level |
| add_evidenceB | Add a new evidence or achievement and link it to the appraisal goals it fulfills |
| list_evidencesC | List all stored evidences with optional filters |
| generate_reportA | Generate a full markdown report of evidences organized by rubric and goal, saved to Obsidian |
| update_evidence_imageB | Attach or replace the image of an existing evidence using the latest image in the Inbox folder |
| generate_summaryA | Generate a mid-year appraisal summary note in English, Spanish, or both, saved to the Obsidian vault |
| generate_game_planB | Generate an actionable game plan for completing remaining appraisal goals, with an accomplishments list for the supervisor and optional current initiatives section |
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 7 tools
Each tool has a clearly distinct purpose: generating different outputs (report, summary, game plan), managing evidences (add, list, update image), and retrieving appraisal goals. No two tools overlap in functionality.
All tool names follow the verb_noun pattern consistently (e.g., generate_report, add_evidence, get_appraisal). The verbs are diverse but descriptive, and there is no mixing of naming conventions.
With 7 tools, the server covers core workflows for an appraisal tracker without being bloated or insufficient. The number fits the domain well.
The tools cover adding and listing evidences, updating evidence images, and generating various reports. However, missing update/delete for evidences and any CRUD for appraisal goals (only get) leaves noticeable gaps for a complete lifecycle.