Skip to main content
Glama
cturkieh

France Data MCP

by cturkieh
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

autocomplete_commune

Read-onlyIdempotent

Search French communes by name, postal code, or INSEE code to autocomplete addresses in forms.

Instructions

Recherche de communes françaises par nom, code postal ou code INSEE. Idéal pour autocomplétion. Source : geo.api.gouv.fr (DINUM/Etalab).

Un (au moins) parmi nom, codePostal, code est requis. Alias acceptés : q/query/search → nom, codepostal/postal_code → codePostal, code_insee/insee → code.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nomNoRecherche par nom (autocomplétion). Ex: "Villeneuve d'Ascq", "Lyon".
codeNoCode INSEE exact (5 caractères). Ex: "59009".
limitNoNombre max de résultats (1-30, défaut 10).
codePostalNoCode postal exact (5 chiffres). Ex: "59650".
boostPopulationNoTrier par population décroissante. Recommandé pour les noms ambigus (ex: 'Charleville').

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.20.0
  2. Removedv0.12.2
  3. Addedv0.10.3
  4. Removedv0.10.0
  5. Addedv0.9.3
  6. Removedv0.9.2
  7. Changed3 schema fields changedv0.9.0
    • changedInput schema / properties / code / description
      Previous value: -"Code INSEE exact (5 caractères)."New value: +"Code INSEE exact (5 caractères). Ex: \"59009\"."
    • changedInput schema / properties / codePostal / description
      Previous value: -"Code postal exact (5 chiffres)."New value: +"Code postal exact (5 chiffres). Ex: \"59650\"."
    • changedInput schema / properties / nom / description
      Previous value: -"Recherche par nom (autocomplétion)."New value: +"Recherche par nom (autocomplétion). Ex: \"Villeneuve d'Ascq\", \"Lyon\"."
  8. First observedv0.7.6

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already indicate read-only, idempotent, and non-destructive behavior. The description adds value by stating that at least one of nom, codePostal, or code is required, which is a key behavioral constraint not fully captured in the input schema (no required parameters).

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

Conciseness5/5

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

The description is three sentences long, front-loaded with purpose and source, then constraints, then aliases. Every sentence adds value with no redundancy or fluff.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description covers purpose, constraints, and aliases well, but with no output schema, it could mention what the tool returns (e.g., a list of communes with basic fields). This omission slightly reduces completeness for a tool with 5 parameters.

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 baseline is 3. The description adds semantic value beyond the schema by providing aliases (e.g., q/query → nom) and explicitly stating the requirement for at least one parameter. The schema also includes examples, but the description's aliases enhance discoverability.

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 description clearly states the tool searches French communes by name, postal code, or INSEE code, and is ideal for autocomplete. It is specific but does not explicitly differentiate from sibling get_commune_by_code, which might be more appropriate for exact code lookup.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides minimal usage guidance: it notes the tool is ideal for autocomplete and mentions the data source. However, it does not specify when to use this tool over siblings like get_commune_by_code, nor does it state when not to use it.

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

Deploy Server

Other Tools