CompleteMCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FIRECRAWL_API_KEY | No | Your Firecrawl API key (only required for scraping job descriptions by URL) |
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_jdA | Get a job description from a URL, pasted text, or a file. Returns JD content, slug, and output paths. Provide exactly one of: url, text, or file_path. Optionally provide a slug like 'CompanyName_Role' for cleaner filenames. |
| get_base_resumeA | Returns the bundled base_resume.json (source of truth) with a job summary showing bullet counts per position. |
| set_base_resumeA | Replace the bundled base resume with a new one. Pass the full resume JSON as a string. This becomes the new source of truth for validation. |
| get_tailoring_rulesA | Returns the resume tailoring rules. Read these before creating any tailored resume. |
| list_skillsA | List the bundled resume/JD tailoring skills with a short description of each. Read the relevant skills (especially the fabricators) before tailoring a resume, then fetch full content with get_skill. |
| get_skillA | Return the full SKILL.md content for one bundled skill. Use the exact name from list_skills (e.g. 'resume-tailor-fabricator'). |
| save_tailored_resumeA | Save a tailored resume JSON. Writes to data/.json by default, or to a custom path. |
| validate_resumeA | Validate a tailored resume JSON against the base resume. Checks identity, fabrication count (max 10), bullet count guardrails, and hedging phrases. |
| build_docxA | Build a DOCX resume from a tailored JSON file. Should only be called after validate_resume passes. Output filename is derived from the base resume Contact.Name. |
| list_jdsA | List all saved job description files with titles and filter status. |
| list_resumesA | List all generated resume files — tailored JSONs and built DOCXs. |
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 11 tools
Each tool has a distinct, non-overlapping purpose. For example, get_jd handles JD input, list_jds lists saved JDs, and get_base_resume vs set_base_resume are clearly separate for reading vs writing the base resume.
All tools use a consistent verb_noun snake_case pattern (e.g., get_jd, set_base_resume, validate_resume). Minor plural/singular variations (list_jds vs get_skill) do not detract from overall predictability.
11 tools cover the core resume tailoring workflow without unnecessary extras. The count is well-scoped for the domain, offering enough granularity without being overwhelming.
The tool surface covers the full pipeline from JD acquisition to DOCX generation, with validation and listing. However, a tool to retrieve the content of a saved tailored resume is missing, which may force file-level access.