Skip to main content
Glama

Vocaneo

by com.vocaneo

Rechercher un métier

search_jobs
Read-only

Recherche des métiers dans le référentiel français Vocaneo : par mots-clés, secteur d'activité, salaire minimum, facilité d'accès au métier ou par thèmes tels que le télétravail, le freelance, les métiers en tension ou à impact écologique. Renvoie une liste courte avec, pour chaque métier, son URL publique à citer. Avec « query », les résultats sont classés par pertinence — le métier généraliste d'abord, puis ses spécialisations : le premier résultat est celui que vise une question « comment devenir X ». Renvoie « results », une page d'au plus 20 métiers, et « total », qui vaut null : l'API des métiers ne fournit pas de décompte. EN: Search French job profiles by keywords, sector, minimum salary, accessibility or themes such as remote work, freelance, high-demand or environmental-impact jobs. Each result carries a public URL to cite. Returns « results », a page of at most 20, and « total », which is null: the jobs API provides no count.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tagsNoThèmes d'excellence du métier. Valeurs acceptées : salary (bien rémunéré), telework (télétravail possible), freelance (exerçable en indépendant), demand (métier en tension, qui recrute), ecological_impact, social_impact. EN: Job themes. Accepted values: salary, telework, freelance, demand, ecological_impact, social_impact.
limitNoNombre de résultats, 1 à 20 (défaut 10). EN: Number of results, 1 to 20 (default 10).
queryNoRecherche libre sur le titre, le code ROME, le secteur et les appellations du métier. Cherche aussi dans le libellé du secteur : « sante » suffit pour les métiers de la santé. EN: Free-text search over job title, ROME code, sector and alternative job names.
sectorsNoIdentifiants de secteurs d'activité, obtenus via l'outil list_job_sectors. Pour une recherche thématique simple, préférer « query ». EN: Sector identifiers, obtained from the list_job_sectors tool.
romeCodeNoCode ROME exact, de la forme M1805. EN: Exact ROME code, e.g. M1805.
minSalaryNoSalaire annuel brut minimum, en euros, comparé au premier décile du métier. EN: Minimum gross annual salary in euros, compared to the job's first decile.
minAccessibilityScoreNoBorne basse du score d'accessibilité du métier, de 0 à 10 : plus il est haut, plus le métier est accessible sans longues études. Utiliser 7 ou plus pour « sans faire de longues études ». Ce score ne mesure pas un niveau de diplôme. EN: Lower bound of the job's accessibility score (0-10): the higher, the easier to enter without long studies. Use 7 or more for « without long studies ». It does not measure a diploma level.

TDQS

A4/5.0
Behavior5/5

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

Beyond the readOnlyHint=true annotation, the description discloses several genuinely non-obvious behaviors: results are capped at 20 per page, « total » is always null because the API provides no count, each item carries a public URL to cite, and query results rank the generalist job first followed by its specializations. These are exactly the traits an agent needs to avoid hallucinating totals or mis-reporting the first result.

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?

The description is front-loaded: the first sentence establishes resource and search dimensions, then return format, then ordering semantics, then the results/total contract. The bilingual FR/EN duplication doubles length, but each language copy is tight and every clause carries information rather than padding.

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

Completeness4/5

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

For a 7-parameter read-only search tool with 100% schema coverage and no output schema, the description covers the top-level return contract (results, total), the per-item URL to cite, and the API's null-count quirk. The remaining gaps are explicit sibling routing (get_job for a single profile, get_similar_jobs for similarity) and per-item fields beyond the URL.

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

Parameters4/5

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

Schema coverage is 100% and all 7 parameters are richly described in the schema, so the baseline is 3. The description adds value beyond the schema by explaining the query-dependent ranking semantics (generalist first, then specializations, first result targets « comment devenir X »), which the schema's query entry does not mention.

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

Purpose4/5

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

The description states a specific verb and resource: « Recherche des métiers dans le référentiel français Vocaneo », and enumerates the search dimensions (keywords, sector, salary, accessibility, themes) plus the list-shaped return of at most 20 jobs. This structurally separates it from siblings like get_job or search_certifications, but no sibling is ever named, so differentiation remains implicit rather than explicit.

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

Usage Guidelines3/5

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

No when-to-use vs alternatives guidance is present; none of the 12 siblings are mentioned and no exclusions are given. Usage context is implied through the query-ordering note (« le premier résultat est celui que vise une question comment devenir X »), and the schema rather than the description points to list_job_sectors for sector identifiers.

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