Skip to main content
Glama
Sirenic MCP server

Sirenic MCP server

Official

French company changes (BODACC)

get_french_company_changes
Read-only

Retrieve new BODACC announcements for a French company since a given date to monitor insolvency, deregistration, sales, filings, and changes in a portfolio.

Instructions

Company monitoring for France: new official BODACC gazette announcements for a French company SINCE a given date (poll-mode watchlist surveillance for a portfolio), such as insolvency, deregistration, sales, filings and changes, in reverse-chronological order. Detects new BODACC publications, not field-level edits of the profile. A company with no new announcement returns an empty list. Judgments in closed fields (category, appointed officers by role and form, date of cessation of payments), never the judgment's text nor a natural person's name; withheld labels are counted in omissions. Paid via x402 ($0.01 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": {
      "siren": "<siren>",
      "depuis": "<depuis>"
    },
    "name": "get_french_company_changes"
  }
}

Input Schema

NameRequiredDescriptionDefault
sirenYes9-digit SIREN
depuisYesList announcements since this date (YYYY-MM-DD)

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
Behavior5/5

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

Goes well beyond readOnlyHint/openWorldHint: it discloses ordering, the empty-list outcome when nothing is new, that judgments are exposed only as closed fields with withheld labels tallied in `omissions`, the x402 payment cost ($0.01 USDC/EURC), and the obligation to cite `citation` verbatim. These are exactly the operational details an agent needs before calling.

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 purpose and scope, then boundary, data-shape caveats, and payment/citation rules in a sensible order. It is dense and parenthetical-heavy, but nearly every clause carries information; only minor tightening is possible.

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, so return structure need not be re-explained; the description nevertheless flags the salient output properties (closed judgment fields, `omissions`, `citation`). For a two-parameter read-only lookup, nothing an agent needs to invoke or interpret it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so both parameters are already documented. The description reinforces the inclusive 'since' semantics of `depuis` but adds no format or edge-case detail beyond the schema, which is the expected baseline here.

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 (retrieve/detect new announcements), a specific resource (official BODACC gazette announcements for a French company), and a scope (since a given date, reverse-chronological). It also draws a sharp boundary: 'Detects new BODACC publications, not field-level edits of the profile', which separates it from profile-update and search-style siblings.

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

Usage Guidelines4/5

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

Gives a clear use case — 'poll-mode watchlist surveillance for a portfolio' — and an explicit exclusion (not field-level profile edits). It does not name a sibling alternative for one-off searching (e.g. search_bodacc_announcements), so the routing advice is strong but not complete.

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