Projet Ariane — Orientation

Rechercher des offres d'emploi ou d'alternance

rechercher_offres

Read-only

Trouve des offres d'emploi et d'alternance actives (France Travail, La Bonne Alternance) par métier ou mot-clé et par ville, département ou région, avec contrat, salaire, date et lien vers l'offre (données Projet Ariane). Avec ville et rayon_km : offres autour de la commune, les plus récentes d'abord, avec la distance à vol d'oiseau.

Input Schema

Name	Required	Description	Default
`type`	No	alternance = apprentissage et professionnalisation ; emploi = hors alternance ; tous (défaut).	tous
`ville`	No	Commune (ex. Cholet, Saint-Étienne), ou département ou région (ex. Rhône, Bretagne). Avec rayon_km, centre de la recherche.
`limite`	No	Nombre de résultats (défaut 6, maximum 20).
`metier`	Yes	Métier ou mots-clés de l'intitulé, sans la ville (ex. boulanger, développeur web).
`rayon_km`	No	Rayon autour de la ville, en km (1 à 300) : offres de la zone, les plus récentes d'abord, avec la distance à vol d'oiseau. Exige ville.
`code_postal`	No	Code postal de la ville, pour départager les homonymes (ex. 93200 pour Saint-Denis).
`departement`	No	Département ou région, nom ou numéro (ex. Rhône, 69, Bretagne).

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedOct 8, 2026

addedInput schema / properties / code_postal

Added value: +{
+  "description": "Code postal de la ville, pour départager les homonymes (ex. 93200 pour Saint-Denis).",
+  "maxLength": 5,
+  "minLength": 5,
+  "type": "string"
+}

addedInput schema / properties / departement

Added value: +{
+  "description": "Département ou région, nom ou numéro (ex. Rhône, 69, Bretagne).",
+  "maxLength": 100,
+  "type": "string"
+}

changedInput schema / properties / metier / description

Previous value: -"Métier ou mots-clés de l'intitulé (ex. boulanger, développeur web)."New value: +"Métier ou mots-clés de l'intitulé, sans la ville (ex. boulanger, développeur web)."

addedInput schema / properties / rayon_km

Added value: +{
+  "description": "Rayon autour de la ville, en km (1 à 300) : offres de la zone, les plus récentes d'abord, avec la distance à vol d'oiseau. Exige ville.",
+  "maximum": 300,
+  "minimum": 1,
+  "type": "integer"
+}

changedInput schema / properties / ville / description

Previous value: -"Ville ou zone (ex. Marseille)."New value: +"Commune (ex. Cholet, Saint-Étienne), ou département ou région (ex. Rhône, Bretagne). Avec rayon_km, centre de la recherche."

AddedSep 15, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, openWorldHint=false, destructiveHint=false), and the description adds real behavioral context: only active offers, results sorted most-recent-first, distance measured as the crow flies, and the upstream sources. It stops short of mentioning pagination limits or auth, but the added traits are substantive.

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?

Two dense sentences with no filler, and the primary capability is front-loaded before the geo-mode detail. The first sentence is heavily packed, but every clause (sources, filters, returned fields) earns its place.

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?

With no output schema, the description usefully enumerates returned fields (contrat, salaire, date, lien) and covers the geo/radius behavior for a 7-parameter tool. It is largely complete, missing only edge-case behavior such as empty results or how metro/region strings are resolved.

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%, so the baseline is 3, but the description adds semantics the schema lacks: the interaction between ville and rayon_km, the recency sort order, and the returned distance metric. This is meaningful meaning beyond the per-field descriptions.

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 gives a specific verb (Trouve) plus resource (offres d'emploi et d'alternance actives), names the data sources (France Travail, La Bonne Alternance, Projet Ariane) and the fields returned. This resource is clearly distinguishable from siblings like rechercher_formation or rechercher_metier without opening any schema.

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?

It explains a concrete usage mode ("Avec ville et rayon_km : offres autour de la commune, les plus récentes d'abord") which tells the agent how to combine geo parameters for a radius search. However it names no alternatives and gives no when-not guidance, so it stops short of a 5.

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

All Projet Ariane — Orientation tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?