Skip to main content
Glama

BODACC Creditor Opposition Deadline Sentinel (France)

French creditor objection deadline lookup (BODACC, by SIREN)

oppositions_lookup
Read-onlyIdempotent

Use this when you need to know whether a French company that owes you money is selling its business, merging or demerging, and until what date its creditors can object. For 1 to 50 SIREN numbers: business sales (fonds de commerce), mergers, demergers and partial asset transfers published in the BODACC in the last 12 months, the last day to object (10 days for a business sale, art. L141-14 Code de commerce; 30 days for a merger, art. R236-11), days left and where to serve the objection. Price: 0.01 USDC per call (x402). Free trial: set free_trial to true (3 calls per day per caller).

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": {
      "sirens": "<sirens>"
    },
    "name": "oppositions_lookup"
  }
}

Input Schema

NameRequiredDescriptionDefault
sirensYes1 to 50 SIREN (9 digits) or SIRET (14 digits) of the debtors, comma-separated
free_trialNoSet to true to ask for the free trial (3 calls per day per caller, shared with the web route, within a daily cap for the service). Without it, the tool asks for an x402 payment.

Output Schema

NameRequiredDescriptionDefault
sourceNo
licenceNoLicence of the source data: nom, url, source, attribution (the credit the licence requires)
resultatsNo
date_calculNo
avertissementNo
entreprises_avec_delai_ouvertNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / free_trial
      Added value: +{
      +  "description": "Set to true to ask for the free trial (3 calls per day per caller, shared with the web route, within a daily cap for the service). Without it, the tool asks for an x402 payment.",
      +  "type": "boolean"
      +}
  2. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the description's job is to add operational context, which it does: a 12-month BODACC lookback window, the statutory objection periods (10 days business sale, 30 days merger), and per-call pricing of 0.01 USDC via x402. It also discloses the free-trial limits (3 calls/day per caller, shared with the web route, subject to a daily cap), which is exactly the kind of quota/auth behavior structured fields cannot express.

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?

Two sentences, front-loaded with the trigger scenario and followed by scope, legal deadlines, price and trial terms; nothing is padding. It is dense and citation-heavy, but each clause carries a fact an agent needs (window, deadlines, cost, quota).

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?

With an output schema present, return values need no explanation, and the description covers the remaining essentials: what events are searched, the lookback horizon, deadline rules, payment model and free-trial quota. An agent can decide to call it and budget accordingly without further information.

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 the sirens pattern/limit and free_trial semantics are already documented in the schema. The description echoes the 1-to-50 SIREN range and free_trial behavior but adds no format or syntax detail beyond it, so the baseline 3 applies.

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 specific verb+resource: checking BODACC-published business sales, mergers, demergers and partial asset transfers for given SIRENs, plus creditor objection deadlines. That is concrete and distinguishable from a generic company lookup. It stops short of naming or contrasting the sibling oppositions_example, so it is clear but not sibling-differentiated.

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?

The opening 'Use this when you need to know whether a French company that owes you money is selling its business...' gives a clear triggering context and implicitly scopes the tool to debt-collection scenarios. It does not state when NOT to use it, nor does it point to any alternative when the 12-month window is insufficient, which keeps it below 5.

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.