Skip to main content
Glama

Mitoyens, pesticides près de chez vous

Classer les communes par exposition

rank_communes
Read-onlyIdempotent

Classement paramétrique des communes par exposition. Paramètres : département, seuil de population, tri (indice combiné, percentile, population), sens (order : desc par défaut, valeurs les plus hautes en premier ; asc pour l’inverse, donc les communes les moins exposées avec le tri par indice ou percentile) et taille du top. Peut renvoyer plusieurs communes d’un même département.

Source : Mitoyens (mitoyens.fr) — Licence Ouverte 2.0 (Etalab), réutilisation libre avec mention de la source. Parcelles RPG 2025 · Données BNVD 2024 arrêtées au 31 décembre 2024 · indice Rigal & Perrot, édition 2025 — données 2013-2022 · eau du robinet SISE-Eaux 2025.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "rank_communes"
  }
}

Input Schema

NameRequiredDescriptionDefault
deptNoCode département (ex. 33, 2A). Un département d’outre-mer (971…) est accepté mais renvoie une liste vide : le classement ne couvre que la métropole et la Corse. Un code inconnu renvoie une erreur not_found.
sortNoCritère de tri (défaut : indice d’exposition combiné).
limitNoTaille du top (défaut 10).
orderNoSens du tri : desc = valeurs les plus hautes en premier (défaut, les plus exposées), asc = les plus basses en premier (les moins exposées ; les moins peuplées avec sort=population).
min_populationNoSeuil de population.

Output Schema

NameRequiredDescriptionDefault
deptYes
sortYes
countYes
orderYes
communesYes
attributionYes
minPopulationYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / dept / description
      Previous value: -"Code département métropolitain (ex. 33)."New value: +"Code département (ex. 33, 2A). Un département d’outre-mer (971…) est accepté mais renvoie une liste vide : le classement ne couvre que la métropole et la Corse. Un code inconnu renvoie une erreur not_found."
  2. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false and idempotentHint=true, so safety is covered structurally. The description adds two genuinely useful behavioral notes: results may contain several communes sharing a name in one department, and the ranking is a fixed parametric ordering. However, the long source/licence block is attribution rather than behavior, and nothing is said about result limits or determinism beyond the schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose statement is front-loaded and clear, but the middle sentence is a near-verbatim walkthrough of five parameters that the schema already documents at 100% coverage, which is wasted space. The trailing source/licence block is legally justified but occupies roughly half the description with data-vintage details an agent rarely needs to act.

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 an output schema present and all five parameters fully documented, the description covers the remaining burden: what the ranking is, what each sort direction means, and where the data comes from and how current it is. The only shortfall is the absence of any routing hint against the seven sibling tools.

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, and the description does go slightly further by giving the concrete meaning of the order parameter in combination with each sort criterion ('asc ... les moins peuplées avec sort=population'), which helps an agent pick asc/desc correctly. Most of the parameter enumeration (department, population threshold, top size) simply restates schema fields, and the DOM-territory caveat lives in the schema rather than the description.

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 opening sentence names a specific verb and resource ('Classement paramétrique des communes par exposition'), so the agent knows this returns a ranked list rather than a lookup or comparison. It even hints at a distinguishing trait ('Peut renvoyer plusieurs communes d'un même département'), but never names search_communes or compare_communes, so the boundary is inferred 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 only implied by the word 'classement' and by the tri/sens parameters: an agent can guess this is for ranked/top-N questions rather than point lookups. There is no explicit when-to-use, when-not, or pointer to a sibling such as compare_communes or get_commune_exposure, which is the main gap for a tool family this dense.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources