Skip to main content
Glama

Projet Ariane — Orientation

by fr.projet-ariane
OverviewDiscussionsAdmin

Classement des lycées et collèges

classement
Read-only

Palmarès des lycées (voie générale et technologique ou professionnelle) et des collèges du millésime le plus récent, au niveau national, par région, département ou ville : rang, réussite, valeur ajoutée, lien vers la fiche de l'établissement (données Projet Ariane, source DEPP). Avec ville et rayon_km : établissements classés autour de la commune, au rang national, avec la distance à vol d'oiseau.

Input Schema

NameRequiredDescriptionDefault
typeYeslycees ou colleges.
voieNoPour les lycées : generale_techno (défaut) ou pro. Ignoré pour les collèges.
villeNoCommune (ex. Strasbourg, Saint-Étienne), ou département ou région (ex. Rhône, Bretagne). Avec rayon_km, centre de la recherche.
limiteNoNombre d'établissements (défaut 6, maximum 20).
rayon_kmNoRayon autour de la ville, en km (1 à 300) : établissements classés de la zone, au rang national, avec la distance à vol d'oiseau. Exige ville.
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. 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: -"Nom du département (ex. Bas-Rhin, Gironde)."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) : établissements classés de la zone, au rang national, avec la distance à vol d'oiseau. Exige ville.",
+  "maximum": 300,
+  "minimum": 1,
+  "type": "integer"
+}
    • changedInput schema / properties / ville / description
      Previous value: -"Commune (ex. Strasbourg). Prime sur le département."New value: +"Commune (ex. Strasbourg, Saint-Étienne), ou département ou région (ex. Rhône, Bretagne). Avec rayon_km, centre de la recherche."
  2. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint=false and destructiveHint=false, so the safety profile is covered. The description adds real behavioral context beyond that: the data provenance (Projet Ariane, source DEPP), the geographic aggregation levels, and the special behavior when ville+rayon_km are combined (ranked nationally with straight-line distance).

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 sentences, front-loaded with the core noun (palmarès) and the data returned, with the special mode relegated to the end. Dense but without filler; only slight repetition of schema-level detail keeps it from a 5.

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?

No output schema exists, so the description carries the burden of describing returns, and it does list the key returned fields (rang, réussite, valeur ajoutée, lien vers fiche). Combined with annotations covering the safety profile and full schema coverage of inputs, an agent has enough to call it correctly.

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?

Schema description coverage is 100%, so the schema already documents all seven parameters including enums, defaults, bounds and the ville/rayon_km dependency. The description's second sentence largely restates the ville+rayon_km mode already present in the schema, adding little beyond the baseline.

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?

States a specific resource (palmarès des lycées/collèges) and scope (millésime le plus récent; national, région, département, ville) with the returned metrics spelled out (rang, réussite, valeur ajoutée, lien vers fiche). This is clearly distinguishable from siblings like fiche_ecole or rechercher_ecole, though the description never names them explicitly, so sibling differentiation is implicit rather than stated.

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?

Usage is implied through the description of two operating modes (geographic level vs. ville+rayon_km), which hints at when the tool is appropriate. However, there is no explicit when-to-use guidance, no exclusions, and no pointer to alternative tools for school lookup versus ranking.

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