Skip to main content
Glama

fr_bilans

Read-only

List available INPI/BCE annual filings for a SIREN.

Returns exercise dates, bilan type (C=complet, S=simplifié, K=consolidé), confidentiality status, and turnover. Typically 3-9 years of history.

⚠️ items holds only the filings whose figures are USABLE (the annual-accounts dataset): a confidential or not-yet-keyed filing is absent from it, so the first item is NOT necessarily the latest filed year. depots_sans_donnees names the filings published in BODACC (accounts filing notices, dpc) whose closing date is not in items — filed, but without usable figures here — and avertissement says when one of them closes AFTER the most recent item: the figures you hold are then older than the company's latest accounts. If BODACC fails, the cross-check is missing and partial_errors says so.

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": "fr_bilans"
  }
}

Input Schema

NameRequiredDescriptionDefault
_orgNoOrg (id) de CET APPEL. `oto_list_orgs()`.
sirenYesSIREN number (9 digits).
_groupNoÉquipe (id) de CET APPEL, sous son org parente.
_run_idNoOBLIGATOIRE à chaque appel dès `run_start` ou `data_claim_next` : sans lui, l'écriture sur une ligne réservée est refusée. Hérité seulement si le serveur tient un run actif — n'y compte pas.
_projectNoProjet (id) de CET APPEL — jeton PRIMAIRE. `oto_project(op='list')`.
_instanceNoInstance de connecteur PRÉCISE (un credential exact). `oto_instance(op='list')`.

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.7/5.0
Behavior5/5

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

The annotation only declares readOnlyHint, while the description adds substantial behavior: returned fields, typical history length, the crucial distinction between usable `items` and `depots_sans_donnees`, and `partial_errors` when BODACC fails. It also warns that the first item is not necessarily the latest filed year.

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 definition is front-loaded with the core purpose and then structured around return fields and a warning block. It is dense but every sentence contributes to correct interpretation.

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

Completeness4/5

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

With no output schema, the description does useful work by explaining the key returned collections and the main cross-check failure mode. It does not cover empty results, pagination, or other errors, so it is strong but not fully complete.

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 the schema already documents all six parameters. The description clarifies the SIREN target but adds no extra meaning for `_org`, `_group`, `_run_id`, `_project`, or `_instance` beyond what the schema provides.

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: list INPI/BCE annual filings for a SIREN. Clear, but it does not distinguish this tool from the sibling fr_bilan.

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

Usage Guidelines2/5

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

There is no explicit when-to-use, when-not-to-use, or alternative-routing guidance. The caveats explain how to interpret the returned data, not how to choose this tool over siblings.

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.

Resources