Skip to main content
Glama

Projet Ariane — Orientation

by fr.projet-ariane
OverviewDiscussionsAdmin

Événements d'orientation à venir

evenements_a_venir
Read-only

Liste les événements d'orientation à venir — journées portes ouvertes, salons étudiants et emploi, forums métiers, ateliers, conférences — par ville, département ou région, type et horizon, avec dates, lieu et inscription (données Projet Ariane, OpenAgenda). Avec ville et rayon_km : événements autour de la commune, par date, avec la distance à vol d'oiseau. Ne rend jamais un événement passé.

Input Schema

NameRequiredDescriptionDefault
typeNoType d'événement, parmi : JPO, IMMERSION, SALON_ETUDIANT, SALON_EMPLOI, FORUM_METIERS, ATELIER, CONFERENCE.
joursNoHorizon en jours (défaut 90, maximum 365).
villeNoCommune (ex. Lyon, Saint-Étienne), ou département ou région (ex. Rhône, Bretagne). Avec rayon_km, centre de la recherche.
limiteNoNombre de résultats (défaut 6, maximum 20).
rayon_kmNoRayon autour de la ville, en km (1 à 300) : événements de la zone, par date, avec la distance à vol d'oiseau ; les événements en ligne sont exclus. Exige ville.
rechercheNoMots-clés libres (nom d'école, thème…).
code_postalNoCode postal de la ville, pour départager les homonymes (ex. 93200 pour Saint-Denis).
departementNoDépartement ou région, nom ou numéro (ex. Rhône, 69, Bretagne).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / type / description
      Previous value: -"Type d'événement, parmi : JPO, SALON_ETUDIANT, SALON_EMPLOI, FORUM_METIERS, ATELIER, CONFERENCE."New value: +"Type d'événement, parmi : JPO, IMMERSION, SALON_ETUDIANT, SALON_EMPLOI, FORUM_METIERS, ATELIER, CONFERENCE."
    • changedInput schema / properties / type / enum
      Previous value: -[
-  "JPO",
-  "SALON_ETUDIANT",
-  "SALON_EMPLOI",
-  "FORUM_METIERS",
-  "ATELIER",
-  "CONFERENCE"
-]New value: +[
+  "JPO",
+  "IMMERSION",
+  "SALON_ETUDIANT",
+  "SALON_EMPLOI",
+  "FORUM_METIERS",
+  "ATELIER",
+  "CONFERENCE"
+]
  2. Changed4 schema fields changed
    • 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"
+}
    • changedInput schema / properties / departement / description
      Previous value: -"Département (ex. Rhône)."New value: +"Département ou région, nom ou numéro (ex. Rhône, 69, Bretagne)."
    • addedInput schema / properties / rayon_km
      Added value: +{
+  "description": "Rayon autour de la ville, en km (1 à 300) : événements de la zone, par date, avec la distance à vol d'oiseau ; les événements en ligne sont exclus. Exige ville.",
+  "maximum": 300,
+  "minimum": 1,
+  "type": "integer"
+}
    • changedInput schema / properties / ville / description
      Previous value: -"Ville (ex. Lyon)."New value: +"Commune (ex. Lyon, Saint-Étienne), ou département ou région (ex. Rhône, Bretagne). Avec rayon_km, centre de la recherche."
  3. Added

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds a genuinely useful guarantee ('Ne rend jamais un événement passé') and the online-event exclusion in radius mode, but omits result ordering/pagination or output shape detail.

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?

Three dense sentences, front-loaded with the core listing behavior and then the radius variant, with no filler. The parenthetical enumerations and data-source note add length but each carries content.

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, the description still tells the agent what comes back (dates, lieu, inscription; distance in radius mode), which is exactly the burden it must carry for a read-only listing tool whose annotations already cover safety.

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 description coverage is 100%, so the baseline is 3, but the description adds relational meaning the schema does not: ville plus rayon_km acts as a center and yields distance-à-vol-d'oiseau results while excluding online events. That interaction is the key semantic not derivable from isolated parameter 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?

States a specific verb ('Liste') and resource ('événements d'orientation à venir') with enumerated event kinds and the data sources (Projet Ariane, OpenAgenda). The siblings are all fiche_/rechercher_/classement tools over different resources, so the resource itself cleanly separates it.

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?

Explains the two operating modes: lookup by ville/département/région/type/horizon, versus radius search triggered by combining ville with rayon_km. It does not name exclusions or point to a sibling alternative, so it stops short of full when/when-not guidance.

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 toolsInspect
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