Skip to main content
Glama

cadastre

Retrieve cadastral information including district, municipality, plot, and fiscal subdivision data for specific geographic coordinates using France's official Géoplateforme services.

Instructions

Renvoie les informations cadastrales (arrondissement, commune, feuille, parcelle, subdivision_fiscale, localisant) pour une position donnée par sa longitude et sa latitude (source :Géoplateforme (WFS, CADASTRALPARCELS.PARCELLAIRE_EXPRESS)).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
lonYesLa longitude du point
latYesLa latitude du point

Implementation Reference

  • The handler function for the 'cadastre' tool. Logs the input coordinates and delegates to the getParcellaireExpress helper to fetch cadastral data.
    async execute(input: CadastreInput) {
      logger.info(`cadastre(${input.lon},${input.lat})...`);
      return getParcellaireExpress(input.lon, input.lat);
    }
  • Zod schema definition for the tool's input parameters: longitude (lon) and latitude (lat).
    schema = {
      lon: {
        type: z.number(),
        description: "La longitude du point",
      },
      lat: {
        type: z.number(),
        description: "La latitude du point",
      },
    };
  • Core helper function that queries the Géoplateforme WFS service for cadastral parcels (PARCELLAIRE_EXPRESS) within 10m of the point, processes features, calculates distances, and returns the nearest per type.
    export async function getParcellaireExpress(lon, lat) {
        logger.info(`getParcellaireExpress(${lon},${lat}) ...`);
        // note that EPSG:4326 means lat,lon order for GeoServer -> flipped coordinates...
        const cql_filter = `DWITHIN(geom,Point(${lat} ${lon}),10,meters)`;
    
        const sourceGeom = {
            "type": "Point",
            "coordinates": [lon,lat]
        };
    
        // TODO : avoid useless geometry retrieval at WFS level
        const url = 'https://data.geopf.fr/wfs?' + new URLSearchParams({
            service: 'WFS',
            request: 'GetFeature',
            typeName: PARCELLAIRE_EXPRESS_TYPES.map((type) => { return `CADASTRALPARCELS.PARCELLAIRE_EXPRESS:${type}` }).join(','),
            outputFormat: 'application/json',
            cql_filter: cql_filter
        }).toString();
    
        const featureCollection = await fetchJSON(url);
        return filterByDistance(featureCollection.features.map((feature) => {
            // parse type from id (ex: "commune.3837")
            const type = feature.id.split('.')[0];
            // ignore geometry and extend properties
            return Object.assign({
                type: type,
                id: feature.id,
                bbox: feature.bbox,
                distance: distance(
                    sourceGeom,
                    feature.geometry
                ),
                source: PARCELLAIRE_EXPRESS_SOURCE,
            }, feature.properties);
        }));
    }
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool returns information (implying read-only) and mentions the data source, but doesn't cover critical aspects like rate limits, authentication needs, error handling, or response format. For a tool with no annotations, this leaves significant gaps in understanding its behavior.

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?

The description is a single, efficient sentence that conveys the core functionality without unnecessary details. It's front-loaded with the main action and resource, though it could be slightly more structured (e.g., separating purpose from data source). Overall, it's concise with no wasted words.

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

Completeness2/5

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

Given the tool's complexity (geographic data lookup with no output schema and no annotations), the description is incomplete. It doesn't explain what cadastral information includes (e.g., details on arrondissement, commune), how results are formatted, or any limitations (e.g., geographic coverage, accuracy). Without annotations or output schema, more context is needed for effective use.

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%, with both parameters (lon and lat) clearly documented in the schema. The description adds minimal value beyond the schema by specifying that these parameters define a position for cadastral lookup, but doesn't provide additional context like coordinate system, valid ranges, or precision requirements. Baseline 3 is appropriate as the schema does the heavy lifting.

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's purpose: it returns cadastral information for a given position specified by longitude and latitude. It specifies the resource (cadastral information) and the action (returns/renvoie), and mentions the data source. However, it doesn't explicitly differentiate this tool from its siblings like 'adminexpress' or 'geocode', which might also handle geographic data.

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 no guidance on when to use this tool versus alternatives. It doesn't mention any prerequisites, exclusions, or compare it to sibling tools like 'adminexpress' or 'geocode', which could be used for similar geographic queries. Usage is implied by the parameters but not explicitly stated.

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