Skip to main content
Glama

Vocaneo

by com.vocaneo

Rechercher un diplôme ou certification

search_certifications
Read-only

Recherche des diplômes et certifications reconnus en France (RNCP, RS) : par nom, par code, par type de diplôme, par niveau de sortie ou par métier visé. Renvoie pour chacun son URL publique à citer. Pour savoir où préparer un diplôme trouvé ici, enchaîner sur search_training_centers avec son certificationId. Renvoie « total », le nombre de diplômes correspondants, et « results », une page d'au plus 20. Quand le référentiel en compte trop pour être dénombrés, « total » vaut null et « totalAtLeast » porte une borne basse : dire alors « plus de N », jamais « N ». EN: Search French recognised diplomas and certifications (RNCP, RS) by name, code, diploma type, exit level or target job. Each result carries a public URL to cite. To find where a diploma is taught, chain to search_training_centers with its certificationId. Returns « total », the number of matches, and « results », a page of at most 20. When the reference data holds too many to count, « total » is null and « totalAtLeast » carries a lower bound: say « more than N », never « N ».

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qNoRecherche libre sur le nom du diplôme et ses codes RNCP ou RS. EN: Free-text search on the diploma name and its RNCP or RS codes.
typeNoType de diplôme. Une trentaine de valeurs, dont : cap_bep, bac, bts_btsa_btsm, but, licence, licence_pro, master, diplome_ingenieur, diplome_etat, titre_professionnel, certification_rs, doctorat. Une valeur non reconnue renvoie une erreur qui énumère la liste complète. EN: Diploma type, about thirty values including cap_bep, bac, bts_btsa_btsm, but, licence, master, diplome_ingenieur, titre_professionnel, certification_rs, doctorat. An unknown value returns an error listing every accepted value.
limitNoNombre de résultats, 1 à 20 (défaut 10). EN: 1 to 20 (default 10).
romeCodeNoCode ROME du métier visé, de la forme J1506, pour ne garder que les diplômes qui y mènent. EN: ROME code of the target job, e.g. J1506.
exitLevelNoNiveau de sortie. Valeurs acceptées : cap_bep, bac, bac_plus_1, bac_plus_2, bac_plus_3, bac_plus_4, bac_plus_5, bac_plus_6, bac_plus_7, bac_plus_8, bac_plus_9_plus, na. Noter la forme avec tirets bas : « bac+3 » n'est pas accepté. EN: Exit level. Accepted values: cap_bep, bac, bac_plus_1 through bac_plus_9_plus, na. Note the underscore form: « bac+3 » is not accepted.

TDQS

A4.4/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The description goes well beyond the readOnly/destructive annotations by disclosing pagination (at most 20 results), the meaning of total, the null-total and totalAtLeast edge case, exactly how to phrase the count ('more than N', never 'N'), and the error behavior for unknown type values. This is rich behavioral context an agent needs to interpret results correctly.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Each substantive point is purposeful and front-loaded, but the full French description is then repeated in English, which roughly doubles the length. The duplication is understandable in a bilingual context, yet it prevents a top conciseness score.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema present, the description compensates thoroughly by defining the returned fields (total, results, URL), the page limit, the totalAtLeast edge case, and the follow-up call to search_training_centers. Nothing essential for correct invocation and interpretation is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Input schema coverage is 100%, with each parameter already documented in detail including accepted values and examples. The description restates the search dimensions at a high level but does not add meaningfully beyond the schema, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names an explicit verb and resource: searching recognized French diplomas/certifications (RNCP, RS). It enumerates concrete search dimensions (name, code, type, exit level, target job) and states the output includes a public URL, clearly distinguishing it from sibling tools such as get_certification or search_training_centers.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives clear usage context and explicitly instructs chaining to search_training_centers with the certificationId to find where a diploma is taught. It does not explicitly exclude alternatives like get_certification, so it stops short of a full when/when-not comparison.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Vocaneo toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.4/5.0
Disambiguation5/5

Each tool targets a clearly distinct resource and action: searches return lists, get tools return single records, and compare_skills, get_similar_jobs, get_job_pathways, and resolve_location each have unique purposes. Even the search_trainings/search_training_centers pair is unambiguous because one yields programmes and the other establishments.

Naming Consistency5/5

All tool names follow a consistent snake_case verb_noun pattern: get_* for records, search_* for queries, plus list_job_sectors, resolve_location, and compare_skills. The slight singular/plural variation between get_training and search_trainings does not break the pattern.

Tool Count5/5

Thirteen tools is well-scoped for a career-guidance server covering jobs, certifications, training programmes, training establishments, location resolution, and skill matching. Each tool earns its place and none feel redundant or decorative.

Completeness5/5

The surface covers the full career-guidance workflow: searching jobs and certifications, retrieving details, finding pathways, locating nearby training, listing sectors, resolving locations, comparing skills, and exploring similar jobs. Every get tool has a clear search entry point, so there are no dead ends.

Resources