France Geodata

Fr Land Cover

fr_land_cover

Read-onlyIdempotent

Land cover at a point in mainland France: the CORINE Land Cover 2018 class (code and label, e.g. 112 "Discontinuous urban fabric") of the polygon containing the point, with its area. Resolution is 25 ha mapping units, so it describes the surrounding area, not the exact spot. found:false when the point is outside the coverage (sea, abroad, overseas).

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "lat": 45.764,
      "lon": 4.8357
    },
    "name": "fr_land_cover"
  }
}

Input Schema

Name	Required	Description	Default
`lat`	Yes	Latitude (WGS84).
`lon`	Yes	Longitude (WGS84).

Output Schema

Name	Required	Description	Default
`found`	No
`point`	No
`level1`	No
`source`	No
`class_code`	No
`data_as_of`	No
`class_label`	No
`polygon_area_ha`	No
`resolution_note`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 26, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already establish readOnly/openWorld/idempotent/non-destructive, so the description earns credit for adding substantive behavioral context: the 25 ha mapping-unit resolution caveat (it describes surroundings, not the exact spot) and the found:false fallback for non-covered points. It does not need to re-explain return values since an output schema exists.

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?

Three tightly packed sentences, front-loaded with the core resource and output, followed by the two constraints that matter (resolution and coverage). No filler or redundancy.

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 a simple two-parameter tool with rich annotations and an output schema, the description covers everything an agent needs: what is returned, the resolution limitation, and the out-of-coverage behavior. Nothing material is missing.

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 lat and lon documented as WGS84 numbers, so the schema already carries the full parameter burden. The description adds nothing per-parameter beyond confirming the tool takes a point, so baseline 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 names a specific resource (CORINE Land Cover 2018 class of the polygon containing a point), the precise output fields (code, label, area), and the geographic scope (mainland France). This is concrete enough that an agent can distinguish it from fr_commune, fr_flood_zones, or fr_buildings_near without opening the schema.

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?

The description implies when the tool applies (querying a point for land cover) and clarifies the out-of-coverage case (sea, abroad, overseas → found:false), but it never names an alternative sibling or an explicit when-not-to-use condition. Usage context is implied rather than stated.

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

All France Geodata tools Inspect

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.