Skip to main content
Glama

TOISE — intelligence foncière

Portefeuille de terrains du compte (lecture)

toise_portefeuille
Read-onlyIdempotent

Où en est mon portefeuille de terrains : liste, statuts, répartition. Modes liste, fiche, echeances, pipeline, etat_locatif (baux, WALT/WALB), transactions, valorisation (DCF, avis de valeur). 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_portefeuille"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNoTexte (intitulé, adresse) ; etat_locatif…
modeNoDéfaut liste ; fiche si terrain_id.
etapeNo
limiteNo
statutNo
communeNo
curseurNo
hypothesesNovalorisation : taux_actualisation_pct…
terrain_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 d’éléments (avant pagination).
ciblesNoPipeline : terrain_id, siren, denomination, etape…
curseurYes
journalNo
partielNotrue : une source n’a pas répondu, des champs manquent…
sourcesYes
terrainNo
deleguesNoTerrains délégués : terrain_id, intitule, commune, statut…
has_moreYes
terrainsNo
warningsYes
echeancesNo
a_relancerNoPipeline : cibles à relancer.
total_borneNoVrai : plafond de 500 terrains, total minimum.
etat_locatifNosynthese (occupation, loyers, WALT/WALB), lignes…
quota_unitesNoUnités d’usage du jour : consommees_par_cet_appel…
transactionsNoTransactions privées du compte, rapprochées de DVF.
valorisationNodcf, capitalisation, sensibilites, avis.
journal_totalNo
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…
plafond_portefeuilleNoNombre de terrains permis par l’offre du compte.
repartition_par_etapeNo
repartition_par_statutNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / q / description
      Previous value: -"Texte (intitulé, adresse) ; etat_locatif : actif."New value: +"Texte (intitulé, adresse) ; etat_locatif…"
  2. First observed

TDQS

B3.4/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 them. The description does add value by disclosing what the etat_locatif mode covers (baux, WALT/WALB) and that valorisation uses DCF and avis de valeur, but it says nothing about pagination behavior, defaults, or that modes return materially different shapes.

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?

A single dense sentence front-loads the purpose, then lists modes, ending with the access mode. No filler, though the parenthetical abbreviations (WALT/WALB, DCF) are packed tightly and the mode list could be easier to scan.

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?

With 9 optional parameters, a nested hypotheses object and multiple modes, an agent needs to know which parameters apply in which mode and what hypotheses keys exist; the description gives only partial hints. The presence of an output schema relieves it of explaining return values, which keeps this from being lower.

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 description coverage is only 33% across 9 parameters, so the description must compensate. It partly does by mapping conceptual views to modes and hinting at hypotheses via 'DCF', but statut, etape, limite, curseur and the terrain_id-to-fiche relationship are left entirely to the enum names and sparse schema text.

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 names a specific resource (portefeuille de terrains) and states what the caller gets back: liste, statuts, répartition, plus an enumeration of the sub-views (baux, transactions, valorisation). It is clear enough to distinguish from generic account or lot tools, but it never explicitly contrasts with siblings such as toise_portefeuille_lot or toise_accords_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?

The mode list implies when each view is appropriate (echeances for schedules, etat_locatif for leases, valorisation for valuation), but there is no explicit when-to-use or when-not-to-use statement, and no routing to alternatives. Usage must be derived from the mode names themselves.

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