Skip to main content
Glama

bodacc_health

Check French company legal health from official BODACC notices using a SIREN/SIRET to surface insolvency, deregistration, sales, account filings, and risk signals.

Instructions

French company legal-health check from the official BODACC notices (DILA open data) for a SIREN/SIRET: insolvency proceedings (sauvegarde, redressement, liquidation), deregistration, sales, accounts filings, last notice dates and a risk summary. Natural persons (sole traders) are masked. Costs 0.003 USDC on Base per successful call (x402). Without a payment key this tool returns the 402 challenge.

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": {
      "siren": "<siren>"
    },
    "name": "bodacc_health"
  }
}

Input Schema

NameRequiredDescriptionDefault
sirenYesSIREN (9 digits) or SIRET (14 digits)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the full load and does well: it discloses the upstream source (official BODACC, DILA open data), privacy behavior (natural persons/sole traders masked), and the x402 payment model including cost, chain, and the 402 challenge on missing key. It does not state what happens for an unknown or malformed SIREN (empty result vs. error), nor any rate limits or idempotency.

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?

Front-loaded with the core purpose, then progressively adds source, masking, and billing details; every sentence carries information. It is dense but not padded, and the payment caveat is placed where an agent will hit it before calling.

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?

No output schema exists, and the description compensates by listing the returned signal categories, but it omits the temporal coverage of the BODACC notices and how missing records are represented. The payment lifecycle is covered, so the remaining gaps are moderate rather than fatal.

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 100% and the single parameter is fully documented in the schema; the description adds the meaningful detail that a 14-digit SIRET is also accepted, matching the schema's allowance. Little else is needed for a one-parameter lookup.

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?

States a specific verb and resource: a legal-health check built from official BODACC/DILA notices for a SIREN/SIRET, and enumerates the signals returned (insolvency, deregistration, sales, accounts filings, last notice dates, risk summary). It does not route against siblings such as fr_company, fr_legal_status or kyb_check_fr, so an agent must infer when this differs from those registry/status tools.

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?

Implies usage (checking French company legal health / insolvency exposure) and clearly flags the payment prerequisite and the 402 challenge without a key. It gives no explicit when-not-to-use guidance and never names an alternative tool for plain registry data or for non-French entities, leaving selection vs. siblings to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.