Skip to main content
Glama
Sirenic MCP server

Sirenic MCP server

Official

Search BODACC announcements

search_bodacc_announcements
Read-only

Search French BODACC legal announcements by family, date window, and department to identify companies in insolvency or other proceedings without knowing their names.

Instructions

Search French BODACC legal announcements by CRITERIA instead of by company, the monitoring question no other Sirenic tool answers: WHICH companies entered insolvency proceedings in department 59 this week? Pick a family (collective/insolvency proceedings, deregistrations, sales and transfers, incorporations, accounts filings, conciliation, professional recovery, modifications, registrations, miscellaneous), a date window (depuis, optional jusqu_a) and optionally a French department code. Returns up to 100 announcements, newest first, each with SIREN, court, town, department and the judgment in closed fields (nature, date, family, category, appointed officers by role and form, never a name, date of cessation of payments), plus tronque when there were more. The judgment's operative FREE TEXT is deliberately removed everywhere (it names court-appointed administrators with their address), so facts living only in that text are NOT here: follow url_bodacc, or get_french_company_legal_alerts for a single company. Announcements about SOLE TRADERS are deliberately EXCLUDED (their name is personal data) and their count is returned in exclues_personnes_physiques, and records whose person type was unreadable are counted apart in exclues_type_indetermine (fail-closed guard). An announcement is not a verdict: the insolvency family also contains closures and cancellations; read the CURRENT state with get_french_company_legal_alerts or get_french_company_default_risk. Paid via x402 ($0.03 in USDC or EURC). When you report a result, cite its citation verbatim.

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": {
      "famille": "<famille>",
      "depuis": "<depuis>"
    },
    "name": "search_bodacc_announcements"
  }
}

Input Schema

NameRequiredDescriptionDefault
depuisYesStart of the publication window, YYYY-MM-DD, e.g. 2026-08-04
familleYesFamily code (upstream BODACC codes): dpc (accounts filings, the largest family), modification, creation, radiation, collective (insolvency proceedings), vente, immatriculation, divers, conciliation, retablissement_professionnel
jusqu_aNoOptional end of the window, YYYY-MM-DD
departementNoOptional French department code: 01-95 except 20, 2A, 2B, 971-978 (e.g. 59 for Nord)

Output Schema

NameRequiredDescriptionDefault
hintNoHow to settle the quote, present when payment_required is true.
quoteNoThe signable x402 payment requirements when payment_required is true: {x402Version, accepts[]} where each entry carries scheme, network, amount, asset and payTo (USDC and EURC options at the same numeric amount). Sign one entry and call again with `x_payment`.
resultatNoThe endpoint's JSON response when payment_required is false. Paid responses carry `source`, `disclaimer` and an Ed25519 signature, and every paid JSON response carries a `provenance` array (all tools since 2026-09-06): one entry per block served, with the official register, licence, version, `empreinte_sha256` (full snapshots), `as_of` date and `precision_as_of` (what that date means), plus the common per-block envelope: `etat` in a closed list (servi, absence_mesuree, absence_non_conclusive, partiel, perime, indisponible, sans_objet), `motif` when unavailable, `age_jours` (only for publication or ingestion dates), `couverture` (complete / partielle / non_mesurable with its measure) and `confiance` in bands (faible / moyenne / forte, only where a measure grounds it, never averaged across blocks). Read the states before the numbers: an absence_non_conclusive, indisponible or partiel block is never « nothing to report »; only absence_mesuree asserts an absence. Register codes: GET /v1/provenance/registres ; states, closed lists and reading rules: GET /v1/lecture (both free). The PDF tools carry no JSON envelope (the PDF report prints it).
free_tierNoFree API key offer for this tool, present with a quote.
payment_requiredYesTrue when this response is an x402 payment quote instead of data: settle one of the quote's `accepts` options and call the tool again with `x_payment`.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds substantial context beyond them: x402 payment of $0.03, the 100-result cap with `tronque`, deliberate exclusion of sole traders with counts in `exclues_personnes_physiques` and `exclues_type_indetermine`, and removal of free text. That is rich disclosure, but the scoring bar is lower when annotations exist, so this sits at a solid 3 rather than higher.

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 question and the criteria-based framing, then layers constraints and caveats. It is dense and long, but nearly every sentence carries operational value; only the family enumeration slightly duplicates the schema.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, yet the description still explains the returned fields (SIREN, court, town, department, judgment nature/date/family, officers by role) and the truncation flag. Combined with payment, exclusion, and citation requirements, an agent has everything needed to call and report correctly.

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%, so the baseline is 3. The description adds meaning by naming the family choices in plain English (insolvency proceedings, deregistrations, sales and transfers, etc.) and by clarifying that `jusqu_a` is optional and `departement` is an optional French department code, helping map intent to the coded schema.

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?

States a specific verb and resource (search BODACC legal announcements) and explicitly contrasts the access mode: 'by CRITERIA instead of by company, the monitoring question no other Sirenic tool answers'. The example question makes the scope concrete and distinguishes it from company-keyed siblings.

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?

Gives explicit when-to-use framing plus named alternatives with conditions: follow `url_bodacc` for free text, use get_french_company_legal_alerts for a single company, and read current state via get_french_company_legal_alerts or get_french_company_default_risk. It also warns that an announcement is not a verdict.

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

Deploy Server

Other Tools