Skip to main content
Glama
Sign In

LegalOne Entreprises

by fr.legalone
OverviewDiscussionsAdmin

List a company's BODACC notices

list_bodacc_notices
Read-onlyIdempotent

Use this when the user asks what was officially published about a company (registration, changes, sale of business, insolvency proceedings, removal) and you know its SIREN: returns the latest BODACC notices, newest first, with links to the official text. Do not use to search notices by person, court decision type or region.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
sirenYesFrench company identifier: 9 digits (spaces allowed).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare this is a read-only, idempotent, non-destructive, closed-world operation. The description adds useful behavioral context beyond annotations: results are the latest notices, ordered newest first, with links to the official text.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two efficient sentences. The primary use case and return behavior are front-loaded, followed immediately by exclusions, with no redundant or filler text.

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?

For a read-only listing tool with rich annotations and no output schema, the description covers the main use case, return ordering, official-text links, and exclusions. The only notable gap is that limit behavior is left entirely to the schema constraints.

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?

The schema documents the required SIREN parameter, while the optional limit parameter only has bounds and a default with no semantic description. The description reinforces that SIREN is the key identifier but does not explain how limit affects the returned list, so it only partially compensates for the 50% schema coverage.

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?

The description gives a specific verb-and-resource pair, 'returns the latest BODACC notices' for a company identified by SIREN, and lists the types of official publications covered. It also distinguishes this listing use case from searching notices by person, court decision type, or region.

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?

It states a clear trigger condition: the user asks what was officially published about a company and the SIREN is known. It also gives explicit exclusions for person, court-decision-type, and region searches, though it does not name the sibling tools that should be used instead.

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

All LegalOne Entreprises toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources