Skip to main content
Glama

TOISE — intelligence foncière

État des lieux d’un assemblage foncier (lecture)

toise_land_assembly
Read-onlyIdempotent

Où en est l'assemblage de parcelles DÉJÀ identifiées pour une seule opération : contiguïté, unité foncière, sécurisation et sentiment propriétaire par parcelle. Entrée : parcelles (IDU) ou terrain_id. Depuis une adresse : d'abord toise_parcelles (rayon), puis cet outil.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "toise_land_assembly"
  }
}

Input Schema

NameRequiredDescriptionDefault
parcellesNoRéférences de parcelles…
code_inseeNo
terrain_idNo

Output Schema

NameRequiredDescriptionDefault
droitNo
liensNoLiens vers la fiche TOISE et vers des services de…
quotaNoQuota du jour après cet appel : { fonction, limite…
curseurYes
partielNotrue : une source n’a pas répondu, des champs manquent…
sourcesYes
has_moreYes
warningsYes
parcellesNoUne ligne par parcelle fournie, dans l’unité foncière ou…
terrain_idNo
quota_unitesNoUnités d’usage du jour : consommees_par_cet_appel…
champs_absentsNoDonnées absentes du résultat partiel.
unite_fonciereNoComposition de l’unité foncière (analyserUnite) : parcelles…
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…
ordre_acquisitionYesToujours null : voir motif_ordre_acquisition.
motif_ordre_acquisitionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered; the description adds what is actually computed per parcel (contiguity, land unit, securing, owner sentiment). It does not mention limits such as the 12-parcel cap or how partial data is reported, but with rich annotations the bar is lower.

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 short sentences, front-loaded with the purpose, then the inputs, then the routing rule. No filler or redundant restatement of the title.

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?

Output schema exists, so return-value explanation is not required, and the description covers purpose, input modes and workflow ordering. The only gap is code_insee and the exact parcelles-vs-terrain_id precedence for a three-parameter tool with no required fields.

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 coverage is only 33%, and the description compensates partially by giving the two input modes ('parcelles (IDU) ou terrain_id') and clarifying that parcelles are IDU references. The third parameter code_insee is explained in neither schema nor description, and the either/or relationship between parcelles and terrain_id is not spelled out as a mutual-exclusion rule.

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?

States a concrete verb and resource — 'Où en est l'assemblage de parcelles DÉJÀ identifiées pour une seule opération' — and enumerates the dimensions assessed (contiguïté, unité foncière, sécurisation, sentiment propriétaire). The capitalised 'DÉJÀ identifiées' explicitly separates this diagnostic tool from parcel discovery, so an agent can distinguish it from toise_parcelles without opening a schema.

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?

Gives an explicit ordered workflow: 'Depuis une adresse : d'abord toise_parcelles (rayon), puis cet outil', naming the sibling and the condition that selects it. It also implies the when-not case (parcels not yet identified) via 'DÉJÀ identifiées'.

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