Skip to main content
Glama

TOISE — intelligence foncière

Accords fonciers d’un terrain (lecture)

toise_accords_fonciers
Read-onlyIdempotent

Où en sont les promesses de vente et compromis d'un terrain de mon portefeuille. Modes accords, fiche, verrouillage, planning, echeances, echeancier (consolidé). Lecture seule.

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_accords_fonciers"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNoaccords
limiteNo
curseurNo
accord_idNoMode fiche : identifiant de l’accord…
terrain_idNo
horizon_joursNoMode echeances : horizon en jours…

Output Schema

NameRequiredDescriptionDefault
finNo
modeYes
debutNo
droitNo
liensNoLiens vers la fiche TOISE et vers des services de…
quotaNoQuota du jour après cet appel : { fonction, limite…
totalNoNombre réel d’éléments (avant pagination).
accordNo
jalonsNo
accordsNo
curseurYes
partielNotrue : une source n’a pas répondu, des champs manquent…
sourcesYes
avenantsNo
has_moreYes
warningsYes
documentsNo
echeancesNo
parcellesNoFiche : parcelles de l’accord ; verrouillage : état par…
conditionsNo
terrain_idNo
quota_unitesNoUnités d’usage du jour : consommees_par_cet_appel…
proprietairesNo
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…
pct_surface_verrouilleeNoNull tant que les surfaces ne sont pas toutes renseignées.
pct_parcelles_verrouilleesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / horizon_jours / description
      Previous value: -"Mode echeances : horizon en jours (défaut 30)."New value: +"Mode echeances : horizon en jours…"
  2. Changed2 schema fields changed
    • changedInput schema / properties / mode / enum
      Previous value: -[
      -  "accords",
      -  "fiche",
      -  "verrouillage",
      -  "planning",
      -  "echeances"
      -]New value: +[
      +  "accords",
      +  "fiche",
      +  "verrouillage",
      +  "planning",
      +  "echeances",
      +  "echeancier"
      +]
    • changedOutput schema / properties / mode / enum
      Previous value: -[
      -  "accords",
      -  "fiche",
      -  "verrouillage",
      -  "planning",
      -  "echeances"
      -]New value: +[
      +  "accords",
      +  "fiche",
      +  "verrouillage",
      +  "planning",
      +  "echeances",
      +  "echeancier"
      +]
  3. First observed

TDQS

B3/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, and the description's 'Lecture seule' merely restates that. Beyond the annotations it adds only the parenthetical '(consolidé)' for the echeancier mode; nothing about pagination via limite/curseur, mode-dependent behavior, or scope of the terrain lookup.

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?

Two short sentences, front-loaded with the business question, followed by the mode inventory and the read-only caveat. No filler; the only weakness is that the mode list is a bare enumeration rather than a structured explanation.

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?

Six optional parameters, an output schema and rich annotations lower the burden, and the description covers the general purpose and the read-only nature. It is still thin on the most consequential piece of complexity — what each mode does and which parameters apply to which mode — so an agent must infer the dispatch logic.

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 only 33%, so the description needs to carry meaning for mode, limite, curseur and terrain_id. It lists the six mode values but this duplicates the schema enum verbatim without explaining what any mode returns, and it never mentions pagination or terrain_id, so it does not compensate for the coverage gap.

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 a concrete resource and question — 'Où en sont les promesses de vente et compromis d'un terrain de mon portefeuille' — so an agent knows it returns agreement/status information for a plot it owns. It then enumerates the modes it exposes. It stops short of differentiating itself from siblings such as toise_droits_fonciers, leaving the boundary to be inferred.

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?

'Lecture seule' and the mode list hint at how the tool is consumed, and the modes themselves read as use cases (fiche, planning, echeances, echeancier). However, no sentence says when to pick this over a sibling, or when one mode is appropriate versus another; usage is only implied.

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