Skip to main content
Glama

TOISE — intelligence foncière

Ma mémoire dealflow

toise_memoire_dealflow
Read-onlyIdempotent

Quel est l'historique de mes recherches et l'activité de mon dealflow sur mon compte. Compte requis ; lecture seule du compte connecté.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
liensNoLiens vers la fiche TOISE et vers des services de…
notesNo
quotaNoQuota du jour après cet appel : { fonction, limite…
depuisNoDate du geste le plus ancien conservé, ou motif d'absence…
sourceYes
curseurYes
lectureNoSynthèse en une phrase.
partielNotrue : une source n’a pas répondu, des champs manquent…
sourcesYes
derniersNoDix derniers gestes.
has_moreYes
par_typeNoDécompte des gestes par type.
warningsYes
evenementsNoNombre de gestes en mémoire pour ce compte…
typologiesNoTypologies/métiers les plus recherchés (5 au plus).
departementsNoDépartements les plus consultés (5 au plus), comptés sur…
quota_unitesNoUnités d’usage du jour : consommees_par_cet_appel…
budget_medianNoBudget médian recherché, ou null si aucune donnée.
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…
surface_mediane_m2NoSurface médiane recherchée, ou null si aucune donnée.
absence_de_resultatNoPrésent si rien n'est encore en mémoire pour ce compte.

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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, non-destructive and closed-world, so "lecture seule du compte connecté" largely restates structured data. The one genuinely additive behavioral fact is the account prerequisite, implying an authenticated session is required. No scope limits (how far back the history goes) or rate/size behavior are described.

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 compact sentences with the subject matter front-loaded and the constraint appended after a semicolon. Nothing is wasted, though the interrogative framing is slightly less direct than a declarative statement would be.

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?

This is a simple, zero-parameter read tool with an output schema, so return formatting need not be explained. The description covers what it returns at a high level and the account requirement; only the depth/scope of the history (time window, volume) is left implicit, which the output schema can absorb.

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?

The tool takes zero parameters, so the baseline is 4 and there is nothing for the description to clarify beyond what the empty schema already conveys. It does not confuse the reader with phantom inputs.

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 the two resources retrieved: search history ("historique de mes recherches") and dealflow activity ("activité de mon dealflow") on the connected account. That is specific enough to distinguish it from data tools like toise_dvf_historique or toise_dealflow, though it is phrased as a user question rather than a verb+resource statement and never names a contrasting sibling.

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?

The only usage information is the prerequisite "Compte requis", which tells the agent an account is needed but not when to pick this tool over the many other account- or dealflow-related siblings. There is no when-not-to-use condition and no named alternative.

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