Skip to main content
Glama

TOISE — intelligence foncière

Négociation foncière et vues d’un terrain (lecture)

toise_negociation_fonciere
Read-onlyIdempotent

Où en est la négociation avec les propriétaires d'un terrain de mon portefeuille. Modes etat, vue, sentiment, operation (multi-propriétaires), historique (contacts). 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_negociation_fonciere"
  }
}

Input Schema

NameRequiredDescriptionDefault
vueNonegocier
modeNoetat
sirenNo
limiteNo
curseurNo
terrain_idYes

Output Schema

NameRequiredDescriptionDefault
vueNo
avisNo
etatNo
modeYes
droitNo
liensNoLiens vers la fiche TOISE et vers des services de…
quotaNoQuota du jour après cet appel : { fonction, limite…
sirenNo
totalNo
accordsNo
curseurYes
legendeNo
partielNotrue : une source n’a pas répondu, des champs manquent…
sourcesYes
has_moreYes
syntheseNo
warningsYes
operationNo
parcellesNo
sentimentNo
echeancierNo
historiqueNo
terrain_idNo
etat_libelleNo
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…

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • changedInput schema / properties / mode / enum
      Previous value: -[
      -  "etat",
      -  "vue",
      -  "sentiment"
      -]New value: +[
      +  "etat",
      +  "vue",
      +  "sentiment",
      +  "operation",
      +  "historique"
      +]
    • addedOutput schema / properties / accords
      Added value: +{
      +  "items": {
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
    • addedOutput schema / properties / echeancier
      Added value: +{
      +  "items": {
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
    • changedOutput schema / properties / mode / enum
      Previous value: -[
      -  "etat",
      -  "vue",
      -  "sentiment"
      -]New value: +[
      +  "etat",
      +  "vue",
      +  "sentiment",
      +  "operation",
      +  "historique"
      +]
    • addedOutput schema / properties / operation
      Added value: +{
      +  "type": "object"
      +}
    • addedOutput schema / properties / synthese
      Added value: +{
      +  "type": "object"
      +}
  2. First observed

TDQS

B3.1/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, and the closing 'Lecture seule' merely restates them. The description does add two useful behavioural hints — that operation mode spans multiple owners and historique mode returns contacts — but says nothing about how results are paged or bounded, which matters for a six-parameter read tool.

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?

Two tight sentences: the question form of the purpose comes first, then the mode inventory, then the read-only qualifier. No filler, no repetition, and each clause carries information.

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 shape need not be described. But for a six-parameter tool with zero schema coverage, the description leaves the vue/verrouiller dimension, the siren filter and the cursor/limit pagination unexplained, which is a real gap for correct invocation.

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 six parameters, so the description must carry the load and only partly does: it glosses four of the five mode values and hints at two of them, but says nothing about the vue parameter (comprendre/negocier/verrouiller), siren, limite or curseur. Half the surface, including the pagination pair, is left 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 description states a concrete purpose: reading the state of the land negotiation with the owners of a plot in the user's portfolio, and it enumerates the available modes. It never names or distinguishes itself from neighbours such as toise_accords_fonciers or toise_droits_fonciers, which is the only thing keeping it from a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use guidance, no indication of how to choose between this tool and the related agreement/rights tools, and no rule for picking one mode over another. The listing of modes implies what can be asked, but the agent must infer the selection logic entirely.

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