Skip to main content
Glama
Sign In

Infoparcelle - cadastre, DVF, DPE, PLU

by fr.infoparcelle
OverviewDiscussionsAdmin

infoparcelle_geocoder_search

Read-onlyIdempotent

🔍 Rechercher des adresses françaises par texte libre avec algorithme de similarité.

Fonction: Convertir une requête textuelle en adresses structurées avec coordonnées GPS.

Retourne:

  • Informations d'adresse complètes (numéro, rue, code postal, ville)

  • Coordonnées GPS (latitude, longitude)

  • Identifiants BAN (Base Adresse Nationale)

  • Parcelles cadastrales associées

  • Score de similarité pour chaque résultat

Cas d'usage principaux:

  • Trouver l'adresse exacte d'un lieu à partir d'une description textuelle

  • Obtenir les coordonnées GPS d'une adresse

  • Identifier les parcelles cadastrales d'une adresse

  • Géolocaliser une adresse partielle ou approximative

  • Rechercher toutes les adresses d'une rue

Exemples de recherche:

  • "7 Rue de l'Élysée 75008 Paris" → Adresse précise

  • "Place de la Concorde" → Lieu connu

  • "Avenue des Champs-Élysées, Paris" → Rue complète

  • "Rue de Rivoli" → Toutes les adresses de cette rue

Conseils:

  • Plus la recherche est précise, meilleurs sont les résultats

  • Les résultats sont triés par similarité (score de pertinence)

  • Utilisez la pagination pour les recherches qui retournent beaucoup de résultats

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "recherche": "<recherche>"
    },
    "name": "infoparcelle_geocoder_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
champsNoListe des champs souhaités dans la réponse
formatNoFormat de sortiejson
limiteNoNombre de résultats par page
curseurNoCurseur de pagination pour la page suivante
champ_triNoChamp de tri (défaut: similarite)similarite
ordre_triNoDirection du tridesc
rechercheYesTerme de recherche (adresse complète ou partielle). Ex: '7 Rue de l'Élysée 75008 Paris'

Output Schema

NameRequiredDescriptionDefault
donneesYes
paginationNoPagination a curseur.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

The annotations already establish that this is a read-only, idempotent, non-destructive search, so the description mainly adds operational context such as similarity sorting and pagination advice. It does not disclose authentication requirements, rate limits, or other behavioral constraints beyond what annotations and the output schema provide.

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 description is front-loaded and well structured with headings and bullet points, but it is lengthy and partly redundant. The return-value section duplicates information available in the output schema, and the examples repeat the usage cases.

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?

Given a 7-parameter tool with full schema descriptions, annotations, and an output schema, the description is complete enough to understand the tool's purpose and basic use. Its main gap is the lack of explicit routing guidance relative to the other geocoder tools.

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. The description reinforces free-text search and mentions pagination and similarity sorting, but adds little parameter-specific meaning beyond the examples already present in the schema.

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 a specific verb and resource: searching French addresses by free text using a similarity algorithm. It explains the conversion into structured addresses with GPS coordinates, but it does not explicitly distinguish this tool from siblings such as infoparcelle_geocoder_ban or infoparcelle_geocoder_coordinates.

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?

It lists several usage cases and examples, which implies when the tool is appropriate, including partial or approximate addresses. However, it never states when not to use it or which sibling tool to choose for coordinate-based lookup versus free-text lookup.

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

All Infoparcelle - cadastre, DVF, DPE, PLU 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