Skip to main content
Glama

Informations d’urbanisme

urbanisme
Read-onlyIdempotent

Retrieve urban planning documents, zones, and regulations for a given longitude and latitude. Access PLU zoning and other regulatory elements from the French Urban Planning Geoportal.

Instructions

Renvoie, pour un point donné par sa longitude et sa latitude, la liste des objets d'urbanisme pertinents du Géoportail de l'Urbanisme (document, zones, prescriptions, informations, etc.), avec leurs propriétés associées. (source : Géoplateforme - (WFS Géoportail de l'Urbanisme)). Les résultats peuvent notamment inclure le document d'urbanisme applicable ainsi que des éléments réglementaires associés à proximité du point. Quand un objet correspond à une couche WFS réutilisable, il expose aussi un feature_ref compatible avec gpf_wfs_get_features et spatial_operator="intersects_feature". Le zonage PLU (zone U, AU, A, N...) est inclus dans les zones retournées et constitue souvent l'information principale recherchée. Pour récupérer exactement l'objet correspondant au feature_ref, utiliser gpf_wfs_get_feature_by_id. Modèles d'URL Géoportail de l'Urbanisme :

  • fiche document: https://www.geoportail-urbanisme.gouv.fr/document/by-id/{gpu_doc_id}

  • carte: https://www.geoportail-urbanisme.gouv.fr/map/?documentId={gpu_doc_id}

  • fichier: https://www.geoportail-urbanisme.gouv.fr/api/document/{gpu_doc_id}/files/{nomfic}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
lonYesLa longitude du point.
latYesLa latitude du point.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultsYesLa liste des objets d'urbanisme pertinents pour le point demandé.
Behavior5/5

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

Annotations already indicate readOnlyHint=true, destructiveHint=false, idempotentHint=true, openWorldHint=true. Description adds context on the nature of results and the feature_ref reuse, enhancing transparency without contradiction.

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?

Description is informative but slightly lengthy; could be more concise. It is front-loaded with the core action and provides necessary details, though some repetition exists.

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

Completeness5/5

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

Given the complexity and presence of an output schema, the description covers all essential aspects: what it does, what it returns, how to link to other tools, and provides URL templates. Sufficient for an agent to invoke 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?

Input schema has 100% coverage with clear descriptions for lon and lat. Description does not add significant meaning beyond what schema already provides, so baseline of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it returns a list of urban planning objects for a given point, specifying source and types (documents, zones, prescriptions). It differentiates itself from siblings by mentioning compatibility with gpf_wfs_get_features and gpf_wfs_get_feature_by_id.

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

Usage Guidelines5/5

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

Provides explicit guidance on when to use this tool (for urban planning info at a point) and references sibling tools for further queries, plus URL models for accessing documents on Géoportail.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ignfab/geocontext'

If you have feedback or need assistance with the MCP directory API, please join our Discord server