job-tracker-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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| add_applicationA | Records a new job application in the tracker. Applied date is set to today automatically. |
| list_applicationsA | Lists tracked job applications, optionally filtered by status and/or a deadline cutoff. |
| update_statusA | Updates a tracked application's status by company name. If multiple applications match the company, none are updated and the matches are listed for disambiguation. |
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
Each tool targets a distinct operation: adding, listing, and updating applications. No overlap in purpose.
All tools follow a consistent verb_noun pattern with snake_case: add_application, list_applications, update_status.
Three tools cover core workflows for a job tracker, though a delete or archive tool might be expected. Count is well-scoped for the domain.
Covers create, read, and update operations, but lacks a delete or archive function, which is a minor gap for full lifecycle management.