Skip to main content
Glama

TOISE — intelligence foncière

Droits de propriété et anomalies d’un terrain (lecture)

toise_droits_fonciers
Read-onlyIdempotent

Qui détient quels droits de propriété sur un terrain de mon portefeuille, parcelle par parcelle. Modes droits et analyse (anomalies, unités foncières). Lecture seule.

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": {
      "terrain_id": "<terrain_id>"
    },
    "name": "toise_droits_fonciers"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNodroits
limiteNo
curseurNo
terrain_idYes
parcelle_idNo

Output Schema

NameRequiredDescriptionDefault
modeYes
droitNo
liensNoLiens vers la fiche TOISE et vers des services de…
quotaNoQuota du jour après cet appel : { fonction, limite…
totalNoNombre réel de droits (avant pagination).
droitsNo
curseurYes
partielNotrue : une source n’a pas répondu, des champs manquent…
sourcesYes
has_moreYes
warningsYes
anomaliesNo
terrain_idNo
quota_unitesNoUnités d’usage du jour : consommees_par_cet_appel…
champs_absentsNoDonnées absentes du résultat partiel.
limite_atteinteNoPrésent quand un quota, une limite d’offre ou une fonction…
paiement_requisNoPrésent quand le résultat complet est un achat à l’acte…
unites_foncieresNo
groupements_fonciersNo
parcelles_sans_geometrieNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so 'Lecture seule' merely restates structured data. What the description does add beyond annotations is mode-dependent behavior – droits yields right-holders, analyse yields anomalies and unités foncières – though it says nothing about permission requirements or what happens when a parcel has conflicting rights.

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?

Three short, front-loaded statements with no filler; the core question ('qui détient quels droits') comes first. The telegraphed noun-phrase style of the mode sentence is slightly elliptical but not wasteful.

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

Completeness3/5

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

An output schema exists, so return values need not be explained, and annotations cover the safety profile. However, for a five-parameter tool with zero schema descriptions, the missing pagination semantics and the terse mode explanation leave gaps an agent would have to guess at.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across five parameters, so the description must carry the burden, and it only glosses the 'mode' enum (droits vs analyse with anomalies/unités foncières). terrain_id and parcelle_id are merely echoed by loose phrasing ('terrain de mon portefeuille', 'parcelle par parcelle'), while 'limite' and 'curseur' pagination behavior is never mentioned.

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 a specific verb and resource – who holds which property rights on a plot – and scopes it to 'un terrain de mon portefeuille' at parcel granularity ('parcelle par parcelle'). It does not explicitly distinguish itself from siblings such as toise_accords_fonciers, but the resource is concrete enough that an agent can tell what it retrieves.

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 'Modes droits et analyse (anomalies, unités foncières)' line implies which mode to pick depending on whether the agent wants holders or anomaly/land-unit analysis, but no explicit when-to-use, when-not, or alternative-tool guidance is given. Usage must be inferred from the two mode labels.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources