EuropassMCP
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_cvA | Start a new, empty CV under a name of your choosing. Pick a short name you will use for the rest of the conversation, such as the surname of the person the CV is for. A name already in use is refused rather than replaced. |
| set_personal_infoA | Record who the CV is about, replacing anything set before. This is the one section a finished CV cannot leave out. Send it again with the full details whenever you learn more; it overwrites rather than merges. |
| add_work_experienceA | Add one job to the CV, after the jobs already added. Add jobs in the order they should be printed, which for a Europass CV is most recent first. |
| add_educationA | Add one qualification or training period, after those already added. |
| add_language_skillA | Add one language the person speaks, with how well they speak it. Add every language separately, mother tongues included. Look the language
code up with |
| add_digital_skillA | Add one digital or computer skill, after those already added. Add every skill as its own call. Europass prints these as free text, so a single call naming several skills is recorded as one skill with a long name rather than as the list it reads like. |
| validate_cvA | Check the draft against the Europass schema and report what is wrong. Safe to call at any point: an unfinished CV is expected to have issues, and each one says where it is and, for a value drawn from a code list, what valid values are spelled most like the one refused. |
| export_xmlA | Write the finished CV as Europass XML. A draft that would not validate is refused rather than exported, so what
comes back is always a schema-valid Europass document. Call |
| export_pdfA | Lay the finished CV out as a PDF, with its Europass XML inside it. Refuses a draft that would not validate, exactly as What comes back is a link rather than the file, because a CV is hundreds of kilobytes and would crowd out the rest of this conversation. Give the link to the user, or read the resource it names if you need the bytes yourself. Refuses a draft whose name cannot be read back out of that link, which is why a draft meant for a PDF wants an ordinary name. |
| lookup_countryA | Find the country codes Europass recognises for a country you can name. Answers a country in any of the languages the schema documents, so both
|
| lookup_languageA | Find the language codes Europass recognises for a language you can name. Each match is a |
| search_occupationA | Find the occupation codes for a job you can describe. These are job titles as the ISCO-88 classification words them, so search for
the profession rather than the person's own job title. Each match is a
|
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
Every tool targets a clear and separate concern: document creation, a specific CV section, validation/export, or a single code-list lookup. Even the lookup tools are unambiguously separated by resource type, and the add_* tools are distinguished by the section they populate.
All tool names follow a predictable lower_snake_case verb_noun pattern: create_, set_, add_, validate_, export_, lookup_, and search_. The add_* family clearly maps to CV sections, and the lookup_* tools consistently represent code-list lookups.
Twelve tools is well-scoped for a CV-building server: one for document creation, four for content sections, one validator, two exporters, and three code-list lookups. There are no redundant or near-duplicate tools inflating the set.
The core Europass sections and the validation/export pipeline are covered, but the entry lifecycle is incomplete: added work, education, language, and digital skill entries cannot be edited or removed, and there is no clean tool for reading back the current CV state. This creates avoidable dead ends when an agent makes a mistake.