Skip to main content
Glama

TOISE — intelligence foncière

BP d’exploitation : hôtel, hostel, résidence gérée

toise_bp_exploitation
Read-onlyIdempotent

Préparer le business plan d'un hôtel, d'un hostel ou d'une résidence gérée : dix ans d'exploitation, TRI et hypothèses sourcées. BP d'un INVESTISSEUR : mode par défaut = celui du préréglage (souvent bail_fixe), à dire ; exploitant : proprietaire_exploitant. Une année : toise_bilan_exploitation.

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": {
      "segment": "<segment>",
      "zone": "<zone>"
    },
    "name": "toise_bp_exploitation"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNoMode d’exploitation…
zoneYesZone de marché.
detteNoSurcharge de financement.dette.
segmentYesSegment d’exploitation.
travauxNoSurcharge de investissement.travaux.
scenarioNoScénario des préréglages (central par défaut).
surface_m2NoSurcharge de capacite.surface_m2.
taux_detteNoSurcharge de financement.taux_annuel.
acquisitionNoSurcharge de investissement.acquisition.
fixes_annuelsNoSurcharge de charges.fixes_annuels.
nombre_unitesNoSurcharge de capacite.nombre.
prix_unitaireNoSurcharge de recettes.prix_unitaire.
occupation_cibleNoSurcharge de recettes.occupation_cible…
personnel_pct_caNoSurcharge de charges.personnel_pct_ca…
loyer_fixe_annuelNoSurcharge de loyer.fixe_annuel.
occupation_departNoSurcharge de recettes.occupation_depart…
loyer_variable_pct_caNoSurcharge de loyer.variable_pct_ca…
mois_montee_en_chargeNoSurcharge de calendrier.mois_montee_en_charge.
taux_capitalisation_sortieNoSurcharge de sortie.taux_capitalisation.
reserve_renouvellement_pct_caNoSurcharge de charges…
commissions_pct_ca_hebergementNoSurcharge de charges…

Output Schema

NameRequiredDescriptionDefault
liensNoLiens vers la fiche TOISE et vers des services de…
quotaNoQuota du jour après cet appel : { fonction, limite…
curseurNo
partielNotrue : une source n’a pas répondu, des champs manquent…
sourcesYes
has_moreYes
lecturesNoLectures exploitant (R), propriétaire (L), promoteur (V).
warningsYes
lien_pageYesPage TOISE portant l’état du calcul…
hypothesesYesChaque hypothèse : cle, valeur, unite, origine…
parametresYessegment, zone, mode, scenario retenus.
indicateursYesIndicateurs du moteur…
quota_unitesNoUnités d’usage du jour : consommees_par_cet_appel…
avertissementNo
compte_annuelYesCompte annuel résumé : annee, occupation, ca, gop, ebitdar…
avertissementsYesAvertissements du moteur : code, message, niveau.
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. First observed

TDQS

A3.8/5.0
Behavior3/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, so the safety profile is covered by structured data. The description adds the ten-year projection horizon and the fact that assumptions are sourced, which is modest behavioral context. It says nothing about computation cost, preset resolution order when overrides conflict, or failure modes, so it does not go far beyond the annotations.

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?

Three short sentences, front-loaded with purpose before the mode routing rule and the sibling pointer; nothing is redundant. The style is telegraphic ('à dire') and slightly elliptical, which costs a little readability but not correctness.

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?

For a 21-parameter, preset-driven model with an output schema available, the description supplies the essentials an agent needs: what is produced, the horizon, how to pick mode, and where to go for a one-year view. It could still clarify that most numeric parameters are overrides layered on a segment/zone/scenario preset, but the schema's 'Surcharge de …' wording partially carries that.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With schema coverage at 100% the baseline is 3, and the description earns an increment by explaining the semantics of the highest-leverage parameter, mode: its default is inherited from the chosen preset and should generally be overridden deliberately depending on whether the BP is for an investor or an operator. The remaining twenty override parameters are left to the schema, which truncates several of its own descriptions, so the compensation is partial.

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 specific verb and resource ('Préparer le business plan d'un hôtel, d'un hostel ou d'une résidence gérée') and adds scope (ten-year operating horizon, IRR, sourced assumptions), which tells an agent exactly what artifact is produced. It also distinguishes itself from the sibling toise_bilan_exploitation ('Une année'), so the boundary is explicit rather than inferred.

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

Usage Guidelines4/5

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

It gives clear routing context: for an investor BP, leave mode at the preset default (often bail_fixe); for an operator BP, set proprietaire_exploitant. It also points to toise_bilan_exploitation for a single-year analysis. What is missing is any when-not guidance (e.g. when to prefer toise_bilan_operation or toise_etude_marche instead), so it stops short of full alternative coverage.

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