Skip to main content
Glama

TOISE — intelligence foncière

Mesures de terrain : altitude, tracé, photos aériennes, trafic et arrêts

toise_mesures_terrain
Read-onlyIdempotent

Altitude, pente, profil altimétrique et distances d'un terrain ou d'un tracé. Modes altitude, profil, mesure, millesimes (photos IGN), autour (arrêts, départs 7h-9h ; temps_tc), ensoleillement (solstices, ombres portées ; géométrique). Pas un relevé de géomètre.

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": {
      "mode": "<mode>"
    },
    "name": "toise_mesures_terrain"
  }
}

Input Schema

NameRequiredDescriptionDefault
latNo
lonNo
modeYes
zoomNoMode millesimes : niveau de zoom de la…
traceNoModes profil et mesure : géométrie GeoJSON…
adresseNo
inclureNoMode autour : trafic, arrets…
rayon_mNo
polygoneNoMode mesure avec un tableau de points…
echantillonsNoMode profil : nombre de points du profil…

Output Schema

NameRequiredDescriptionDefault
modeYes
liensNoLiens vers la fiche TOISE et vers des services de…
pointYes{ lat, lon, adresse_retenue } pour les modes à point ; null…
quotaNoQuota du jour après cet appel : { fonction, limite…
curseurYes
partielNotrue : une source n’a pas répondu, des champs manquent…
sourcesYes
has_moreYes
resultatYesContenu propre au mode : altitude { altitude_m | absent }…
warningsYes
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…

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / polygone / description
      Previous value: -"Mode mesure avec un tableau de points : vrai…"New value: +"Mode mesure avec un tableau de points…"
    • changedInput schema / properties / zoom / description
      Previous value: -"Mode millesimes : niveau de zoom de la tuile…"New value: +"Mode millesimes : niveau de zoom de la…"
  2. Changed2 schema fields changed
    • removedInput schema / properties / mode / description
      Removed value: -"Lecture demandée : altitude, profil, mesure…"
    • changedInput schema / properties / mode / enum
      Previous value: -[
      -  "altitude",
      -  "profil",
      -  "mesure",
      -  "millesimes",
      -  "autour"
      -]New value: +[
      +  "altitude",
      +  "profil",
      +  "mesure",
      +  "millesimes",
      +  "autour",
      +  "ensoleillement"
      +]
  3. Changed2 schema fields changed
    • changedInput schema / properties / inclure / description
      Previous value: -"Mode autour : trafic, arrets, ou les deux…"New value: +"Mode autour : trafic, arrets…"
    • changedInput schema / properties / inclure / items / enum
      Previous value: -[
      -  "trafic",
      -  "arrets"
      -]New value: +[
      +  "trafic",
      +  "arrets",
      +  "temps_tc"
      +]
  4. Changed1 schema field changed
    • changedInput schema / properties / polygone / description
      Previous value: -"Mode mesure avec un tableau de points : vrai pour…"New value: +"Mode mesure avec un tableau de points : vrai…"
  5. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, open world), so the bar is lower. The description adds real domain semantics the annotations cannot convey: IGN photo vintages, the 7h-9h departure window for traffic/stops, and solstice-based shadow modelling. It does not disclose data freshness, precision limits beyond the surveyor caveat, or failure behavior when coordinates are missing.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short and front-loaded with the outputs, with zero filler. However, the mode list is a dense telegraphic run-on with semicolon-separated hints that borders on cryptic, so brevity partly costs clarity.

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. For a 10-parameter, mode-dispatching tool, the critical missing piece is which inputs each mode requires or accepts (e.g. does altitude need lat/lon or adresse; does mesure need trace plus polygone). The description gestures at this mapping but does not complete it.

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 50%, so the baseline is 3. The description does useful mapping work by tying modes to parameter families (millesimes to photos/zoom, autour to arrêts/rayon, ensoleillement to geometric shadow inputs), which helps an agent pick a mode. But lat, lon, adresse, trace, polygone and echantillons are never explained, leaving half the parameters undocumented in both schema and description.

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 first sentence names concrete outputs (altitude, slope, elevation profile, distances) for a specific resource (a terrain or a tracé), and the mode list makes the tool's scope concrete. It also rules out a false expectation with 'Pas un relevé de géomètre'. It does not differentiate from named siblings, but the sibling list contains no obvious measurement alternative, so the gap is minor.

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 parenthetical glosses on modes (millesimes = photos IGN, autour = arrêts/départs 7h-9h, ensoleillement = solstices/ombres) imply when each mode is appropriate. However, there is no explicit statement of the prerequisites per mode (lat/lon vs adresse vs trace) and no 'use X instead' routing. Usage 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.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources