JobApplication
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| JOBAPP_HOME | No | Path to the JobApplication data folder (default: ~/JobApplication-data) |
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 |
|---|---|
| find_jobsC | Search the job sites now (or check on a search already running). |
| list_jobsC | List saved jobs (best match first by default). |
| job_detailsC | Everything about one job, including the description and keyword match. |
| build_resumeC | Build the tailored PDF resume for a job. |
| mark_jobC | Set status: new, interested, applied, interview, rejected, offer, ignored. |
| import_resume_prepareA | Start a resume import from a Word (.docx) or PDF file (docx_path = path to either): returns the prompt to follow. |
| import_resume_submit_texC | Check a LaTeX version of the imported resume against the source Word or PDF file. |
| doctorC | Check the installation and settings; each problem has a fix hint. |
| update_config_filtersB | Change the job filters in config.yaml (only the fields you pass). Old file kept as config.yaml.bak. |
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 9 tools
Most tools target clear distinct actions: search (find_jobs), view saved (list_jobs), inspect one (job_details), build PDF (build_resume), set status (mark_job), import resume (two-step), diagnostics (doctor), and config. The only mild overlap is find_jobs vs list_jobs and the two import_resume_* steps, but descriptions disambiguate them reasonably.
Most tools follow verb_noun (find_jobs, list_jobs, build_resume, mark_job, update_config_filters), but job_details is noun_noun and doctor is a bare noun, breaking the pattern. The import_resume_prepare/import_resume_submit_tex pair is consistent internally but verbose; conventions are mixed though still readable.
Nine tools fit the job-application workflow well, each covering a genuine step (search, inspect, track, build resume, import, diagnose, configure). Nothing feels redundant or padded.
The surface covers the core lifecycle: search, save/list, status tracking, resume build/import, diagnostics, and config. Minor gaps exist (e.g., no delete/remove saved job or note-adding operation), but agents can work around these in the broader workflow.