Skip to main content
Glama

TOISE — intelligence foncière

Mandats d’un dirigeant (autres sociétés)

toise_mandats
Read-onlyIdempotent

Quelles sociétés dirige une personne physique précise : mandats SOCIAUX au registre national des entreprises (rien à voir avec des mandats de vente ou de location). Exige nom, prénom EXACTS et naissance (AAAA-MM, lue dans toise_societe). Compte requis ; aucune coordonnée. Annonces ou dossiers suivis du compte : toise_dealflow ou toise_suivis.

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": {
      "nom": "<nom>",
      "prenom": "<prenom>",
      "naissance": "<naissance>"
    },
    "name": "toise_mandats"
  }
}

Input Schema

NameRequiredDescriptionDefault
nomYesNom de famille exact, tel qu’au registre…
prenomYesPremier prénom exact…
curseurNo
en_directNoVrai : interroger le registre en direct…
naissanceYesMois et année de naissance publiés, AAAA-MM…

Output Schema

NameRequiredDescriptionDefault
liensNoLiens vers la fiche TOISE et vers des services de…
quotaNoQuota du jour après cet appel : { fonction, limite…
totalYesMandats confirmés lus jusqu’ici…
sourceYes
curseurYes
mandatsYesSociétés où la personne est dirigeante : jamais de…
partielNotrue : une source n’a pas répondu, des champs manquent…
sourcesYes
affichesYes
has_moreYes
personneYesCe qui a été recherché, rappelé tel quel : nom, prenom…
warningsYes
millesimeYesDate de lecture du registre en direct, ou date du stock RNE…
garde_fousYesRègles appliquées à cet appel.
informationNoMention d’information des personnes…
quota_unitesNoUnités d’usage du jour : consommees_par_cet_appel…
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. Changed1 schema field changed
    • changedInput schema / properties / prenom / description
      Previous value: -"Premier prénom exact (sans initiale ni joker)."New value: +"Premier prénom exact…"
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

The annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds genuinely new context: an account is required, and the response carries no contact details ('aucune coordonnée'), which bounds what the agent can expect. It does not discuss the live-registry latency or cursor behavior, so it falls just short of a 5.

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?

It is short and front-loaded, with the disambiguation in parentheses carrying its weight. The final sentences are telegraphic ('Compte requis ; aucune coordonnée.'; the toise_dealflow routing drops its verb), which is efficient but slightly terse for a first-time reader.

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 five-parameter, three-required lookup with an output schema and full annotation coverage, the description supplies what structured fields cannot: exact-identity requirements, the source of the birth value, the account prerequisite, and the sibling routing. Only the 'en_direct' vs cached tradeoff and pagination remain unaddressed, and both are covered in the schema.

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?

Schema coverage is 80%, so the baseline is 3, but the description adds meaning the schema does not: it states which three inputs are mandatory and, critically, where the required AAAA-MM birth value comes from (toise_societe). That chain-of-calls hint is real added value across the five parameters.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The opening clause names a specific verb and resource: the 'mandats SOCIAUX' held by an exact natural person in the registre national des entreprises. It explicitly disambiguates from an obvious false friend ('rien à voir avec des mandats de vente ou de location'), so an agent won't confuse it with property mandates.

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

Usage Guidelines5/5

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

The description states both prerequisites (exact surname, exact first name, and birth month read from toise_societe; account required) and an explicit alternative route ('Annonces ou dossiers suivis du compte : toise_dealflow ou toise_suivis'). An agent can decide between this tool and its siblings without inspecting schemas.

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