Skip to main content
Glama
Sirenic MCP server

Sirenic MCP server

Official

French company: everything new since a date

get_french_company_updates_since
Read-only

Lists all official changes for a French company since a date—insolvency, court decisions, contracts, establishment changes, sanctions, trademarks—and flags if coverage is complete.

Instructions

What changed at a French company since a date ("what changed at this customer since June?"): every official block in one call, namely BODACC notices (insolvency, sales, deregistration, changes, accounts filings with their figures), commercial-court decisions, French and EU public contracts, establishments opened or closed, cessation, licences, dated sanctions listings, trademarks, patents and designs, RGE certifications and the lobbying register. Each change is dated at publication (a court decision: the day Sirenic first collected it), with the event date alongside; verdict nouveautes, rien_de_nouveau (every block read in full and fresh) or lecture_incomplete (a block down, stale or partly read, named); monthly stocks (Sirene, French contracts) make a recent date, after their snapshot, yield lecture_incomplete, never rien_de_nouveau; the 100 most recent, per-type totals before the cut. Hiring, officers and headcount band are outside the engine. Paid via x402 ($0.05 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_updates_since"
  }
}

Input Schema

NameRequiredDescriptionDefault
sirenYes9-digit SIREN
depuisYesList what was published since this day, a past day or today. Accepts YYYY-MM-DD (a real date), or a full ISO 8601 timestamp (offset Z, ±HH:MM, ±HHMM or none, read as UTC): only its UTC day is kept.

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

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

Annotations only cover readOnly and openWorld, and the description goes well beyond them: dating semantics (publication date vs. event date, court decisions dated by Sirenic's collection day), the three verdict values and what each means, the monthly-stock snapshot caveat, the 100-record cap with per-type totals before the cut, and x402 pricing at $0.05 in USDC or EURC. It even states an output-citation obligation. The only omission is any note on latency or error behavior for a block that is down.

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 core purpose is front-loaded in the first clause and nearly every following phrase carries operational information rather than filler. Structure is a weakness: the body is one very long sentence with nested parentheticals, so a reader must parse hard to extract the verdict rules and the pricing, which would read better as separate short sentences.

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?

A roll-up tool over many data blocks with an output schema present, so return shape need not be described, and the description still covers dating, verdict semantics, truncation limits, exclusions and payment. Nothing an agent needs to call it correctly or interpret the verdict is missing.

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, but the description adds meaning the schema cannot: 'depuis' is a cut-off day whose interpretation is modulated by monthly stock snapshots, so a very recent date can force lecture_incomplete. It also reinforces that the returned set is the 100 most recent with per-type totals, which shapes how the parameter should be chosen.

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 and pins the scope: 'What changed at a French company since a date,' then enumerates exactly which official blocks are covered (BODACC notices, court decisions, public contracts, establishments, IP, RGE, lobbying). It also declares what is out of scope ('Hiring, officers and headcount band are outside the engine'), which lets an agent separate it from narrower siblings such as the changes, court-decision or procurement tools without opening a schema.

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 concrete usage context with the example query ('what changed at this customer since June?') and states the exclusions, plus a freshness rule about when a recent date yields lecture_incomplete rather than rien_de_nouveau. It never names an alternative tool to use instead when you only want one block type, so routing between this roll-up and the per-domain siblings is left to inference.

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