CareerBot
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CAREERBOT_MCP_HOST | No | Host address for the remote MCP server. | 127.0.0.1 |
| CAREERBOT_MCP_PORT | No | Port for the remote MCP server. | 8000 |
| CAREERBOT_XAI_MODEL | No | The xAI model to use for AI-powered operations. | grok-4.6 |
| CAREERBOT_XAI_API_KEY | Yes | Your xAI API key. Required for model-backed commands such as scoring, tailoring, and cover letter generation. | |
| CAREERBOT_AIRTABLE_PAT | No | Optional Airtable Personal Access Token. Required only if you want Airtable tracking. | |
| CAREERBOT_MCP_TRANSPORT | No | MCP transport type. Use 'streamable-http' for remote clients. | stdio |
| CAREERBOT_MCP_AUTH_TOKEN | No | Bearer token for authenticating remote MCP connections. Strongly recommended for remote setups. | |
| CAREERBOT_MAX_RUN_MINUTES | No | Maximum runtime in minutes for batch operations. | 30 |
| CAREERBOT_AIRTABLE_BASE_ID | No | Optional Airtable Base ID. Required only if you want Airtable tracking. | |
| CAREERBOT_MAX_JOBS_PER_RUN | No | Maximum number of jobs to process per run. | 20 |
| CAREERBOT_MAX_APPLICATIONS_PER_RUN | No | Maximum number of applications to prepare per run. | 5 |
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
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| score_jobB | Score one job against the verified master resume. |
| consult_career_positioningA | Generate a CV-grounded career strategy for review without saving it. |
| save_career_strategyC | Save an explicitly reviewed strategy and an immutable snapshot. |
| get_career_strategyA | Return the currently approved downstream career strategy. |
| search_jobsC | Normalize, rank, and deduplicate permitted supplied job data. |
| tailor_resumeC | Tailor the master LaTeX resume and enforce all deterministic rules. |
| generate_cover_letterB | Generate a concise cover letter grounded in the tailored resume. |
| save_application_snapshotC | Compile and atomically save a complete immutable application package. |
| track_applicationC | Upsert an application in Airtable when configured and in the CSV backup. |
| verify_snapshotB | Verify immutable artifact sizes and SHA-256 hashes. |
| submission_hard_stopsA | Return conditions that always require a manual handoff. |
| assess_submissionC | Decide whether an application can use an authorized automatic connector. |
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 12 tools
Most tools map cleanly to distinct actions: strategy lifecycle, resume/cover letter generation, snapshot verification, and tracking are all clearly separated. The only mild ambiguity is between search_jobs/score_job and submission_hard_stops/assess_submission, where the evaluation and approval responsibilities are adjacent.
Nearly all tools follow a verb_noun snake_case pattern such as save_career_strategy, tailor_resume, and verify_snapshot. The outlier is submission_hard_stops, which is a noun phrase rather than a verb-led action, creating a small but noticeable inconsistency.
Twelve tools is well-scoped for a career-application pipeline covering strategy, job matching, resume/cover letter production, snapshot verification, tracking, and submission assessment. Each tool addresses a distinct stage or artifact, so the count feels purposeful rather than bloated.
The core lifecycle is well covered: strategy approval, job scoring, resume tailoring, cover letter generation, application snapshot creation and verification, tracking, and submission assessment. Minor gaps exist around retrieving past application snapshots and actually executing a submission, though the design may intentionally stop at assessment and manual handoff.