Skip to main content
Glama
Sign In

Aucadastre

by fr.aucadastre
OverviewDiscussionsAdmin

Une parcelle cadastrale francaise par sa reference

get_french_parcel
Read-onlyIdempotent

Une parcelle par son identifiant a quatorze caracteres (code INSEE, prefixe, section, numero, par exemple 940810000E0107) : sa contenance, sa commune, et la voie la plus proche de son centre, dont le jumeau porte tout le reste. Le proprietaire n'y est pas : ceux qui sont des personnes morales se lisent dans le jumeau de la voie, un particulier nulle part.

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": {
      "parcel_id": "<parcel_id>"
    },
    "name": "get_french_parcel"
  }
}

Input Schema

NameRequiredDescriptionDefault
parcel_idYesL'identifiant de la parcelle, quatorze caracteres, par exemple 940810000E0107.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / parcel_id / description
      Previous value: -"L'identifiant de la parcelle, quatorze caracteres, par exemple 94081000AB0123."New value: +"L'identifiant de la parcelle, quatorze caracteres, par exemple 940810000E0107."
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare the tool as read-only, idempotent, non-destructive, and open-world, so the safety profile is covered. The description adds valuable scope details: exactly what is returned (area, commune, nearest road) and what is deliberately excluded (owner identity), which helps the agent understand the data boundaries.

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 two sentences and front-loads the core operation: retrieving a parcel by its identifier. It is dense but efficient, though the reference to a 'jumeau' without naming it slightly reduces immediate clarity.

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?

For a single-parameter, read-only lookup with no output schema and clear annotations, the description covers what the tool returns and its main limitation regarding owner data. Naming the concrete alternative for ownership information would make it fully complete.

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 description coverage is 100%, so the input schema already documents the single parcel_id parameter with its regex pattern and example. The description goes further by breaking the 14-character identifier into its INSEE code, prefix, section, and number components, adding semantic meaning beyond 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 states that the tool returns a French cadastral parcel by its 14-character identifier, including its area, commune, and nearest road. This is a clear verb-resource pairing, but it does not name the sibling tools it contrasts with, referring only to an unnamed 'jumeau' (twin).

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 to use the tool (to get parcel attributes by ID) and when not to use it for ownership information, noting that legal-entity owners are found in the road twin while individuals are not found at all. However, it never names or directly points to the alternative sibling tools, leaving routing implicit.

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

All Aucadastre 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