Skip to main content
Glama

Projet Ariane — Orientation

by fr.projet-ariane
OverviewDiscussionsAdmin

Rechercher des aides financières

rechercher_aides
Read-only

Trouve les aides financières (bourses, logement, mobilité…) pour une situation décrite en texte libre et un lieu (ville, département ou région) : aides nationales et locales (région, département, CAF, commune), les plus locales d'abord, avec portée, montants et liens vers les fiches. Sans lieu, aides nationales seulement.

Input Schema

NameRequiredDescriptionDefault
villeNoCommune (ex. Cholet, Saint-Étienne), ou département ou région (ex. Rhône, Bretagne). La commune où vit la personne.
categorieNoCatégorie d'aide à filtrer. Valeurs acceptées : logement, mobilite, international, equipement, restauration, bourse, emploi, sante, autre. Toute autre valeur est ignorée.
situationYesSituation de la personne en texte libre, sans la ville (ex. étudiant boursier, apprenti, lycéen en mobilité).
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"
+}
    • 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 / situation / description
      Previous value: -"Situation de la personne en texte libre (ex. étudiant boursier, apprenti, lycéen en mobilité)."New value: +"Situation de la personne en texte libre, sans la ville (ex. étudiant boursier, apprenti, lycéen en mobilité)."
    • addedInput schema / properties / ville
      Added value: +{
+  "description": "Commune (ex. Cholet, Saint-Étienne), ou département ou région (ex. Rhône, Bretagne). La commune où vit la personne.",
+  "maxLength": 100,
+  "type": "string"
+}
  2. Changed1 schema field changed
    • addedInput schema / properties / situation / maxLength
      Added value: +500
  3. Changed1 schema field changed
    • changedInput schema / properties / categorie / description
      Previous value: -"Catégorie d'aide à filtrer (ex. logement, transport, alternance)."New value: +"Catégorie d'aide à filtrer. Valeurs acceptées : logement, mobilite, international, equipement, restauration, bourse, emploi, sante, autre. Toute autre valeur est ignorée."
  4. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, non-destructive, closed-world), so the description is free to add substance — and it does: result ordering (most local first), result content (portée, montants, liens vers les fiches), and degradation behavior without a location. This is meaningful behavior beyond the annotations.

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?

A single dense sentence, front-loaded with the verb and resource, followed by the scoping and fallback clauses. Every clause carries information; the parenthetical example lists are the only mild 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?

With no output schema, the description does the work of describing returns (portée, montants, liens) and the ordering, so an agent knows what to expect. Nothing critical is missing, though result volume/pagination is unaddressed.

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% and each parameter is documented there, including the accepted categorie values and the code_postal disambiguation role. The description only restates that location may be a city, department or region and that situation is free text, adding little beyond the schema; baseline 3 applies.

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 verb and resource: "Trouve les aides financières (bourses, logement, mobilité…)" with the input mode (free-text situation + location). It is clearly distinguishable from fiche_aide (detail view) and the rechercher_* siblings by being a situational search, though it never names an alternative explicitly.

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?

Gives clear conditions of use — a free-text situation plus an optional location — and states the fallback when no location is given (national aid only). It stops short of naming alternatives such as fiche_aide for consulting a specific aid, so it is context-rich but not exclusionary.

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