Skip to main content
Glama

TOISE — intelligence foncière

Annonces légales du BODACC

toise_bodacc
Read-onlyIdempotent

Quelles sociétés sont en difficulté ou ont cédé un fonds : annonces légales du BODACC (redressement, liquidation, cessions). Par siren ou departement ; familles vente ou collective, depuis. Un signal, jamais une mise en vente.

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

Input Schema

NameRequiredDescriptionDefault
sirenNo
depuisNoNe garder que les annonces parues à partir…
limiteNo
curseurNo
famillesNoFamilles d'annonces ; par défaut vente et…
departementNo

Output Schema

NameRequiredDescriptionDefault
liensNoLiens vers la fiche TOISE et vers des services de…
quotaNoQuota du jour après cet appel : { fonction, limite…
totalYesNombre réel d'annonces de la source pour le périmètre…
sourceYes
curseurYes
lectureYes
partielNotrue : une source n’a pas répondu, des champs manquent…
sourcesYes
affichesYes
annoncesYes
decalageNo
has_moreYes
warningsYes
millesimeYesDate de parution de la plus récente annonce rendue, ou {…
perimetreYessiren ou departement, familles, depuis.
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…
plafond_visiteurNo
absence_de_resultatNo
personnes_physiques_ecarteesNoAnnonces de la page visant une personne physique…

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / depuis / description
      Previous value: -"Ne garder que les annonces parues à partir de…"New value: +"Ne garder que les annonces parues à partir…"
  2. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds real context beyond that: the legal-announcement source, the event types returned (redressement, liquidation, cessions), and the important interpretive caveat that a hit is a signal and not a listing for sale. Pagination behavior is the main unaddressed trait.

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?

The most useful content — the question answered and the event types — is front-loaded in the first clause, and the whole description is two sentences plus a caveat. The middle clause is telegraphic ('Par siren ou departement ; familles vente ou collective, depuis'), which is efficient but slightly clipped for readability.

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 values need not be described, and the core filters are covered. But two of six parameters, including the cursor used for paging through results, are neither described nor self-explanatory, leaving a real gap for a list-returning tool.

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 only 33% schema description coverage, the description does meaningful work: it explains that lookup can be by siren or departement, that familles takes 'vente' or 'collective' (the enum values themselves lack per-value descriptions in the schema), and that 'depuis' is a time floor. Only 'limite' and 'curseur' (pagination) go unexplained.

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 concrete resource and scope: 'annonces légales du BODACC (redressement, liquidation, cessions)' and frames the question it answers (companies in difficulty or that sold a business). An agent can distinguish it from analysis/valuation siblings without opening the schema. It stops short of explicitly naming a sibling it is not, so 4 rather than 5.

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?

Usage is implied through the filters it lists ('par siren ou departement', 'familles vente ou collective', 'depuis'), and the closing caveat 'Un signal, jamais une mise en vente' usefully bounds how results should be interpreted. However, no explicit when-to-use/when-not or alternative tool is named, so the agent must infer routing.

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