Skip to main content
Glama

fr_legal_status

Check French company legal status by SIREN/SIRET: Sirene administrative state plus BODACC proceedings with latest stage, ongoing flag, and risk level.

Instructions

French company legal status by SIREN/SIRET: Sirene administrative status (active/ceased, closure date, legal form, NAF, head office) plus BODACC collective proceedings (sauvegarde, redressement, liquidation judiciaire, clôture) with latest stage, ongoing flag and risk level. Costs 0.003 USDC on Base per successful call (x402). Without a payment key this tool returns the 402 challenge.

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_legal_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
maxNonotices 1-50
sirenYesSIREN or SIRET

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does meaningful work: it discloses the exact price (0.003 USDC on Base), that billing is per successful call, the x402 payment protocol, and that an unauthenticated call returns a 402 challenge. That is unusually concrete for a paid tool. It does not cover rate limits, failure/refund behavior, or latency, keeping it out of the top score.

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?

Three compact sentences, front-loaded with the resource and its data sources, then the cost model. Dense with domain terms (Sirene, BODACC, sauvegarde, redressement) but each phrase maps to a real returned field, so little is wasted. The payment sentence could be shortened slightly.

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?

There is no output schema, and the description compensates by enumerating the returned concepts: status, closure date, legal form, NAF, head office, proceedings stage, ongoing flag and risk level. Combined with the payment/402 disclosure, an agent has enough to decide and call correctly. The unexplained 'max' bound is the main residual gap.

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 both parameters and a 3 is the appropriate baseline. The description reinforces that the identifier is a SIREN or SIRET but adds no format, length or validation detail, and the 'max' parameter (notices 1-50) is never mentioned in the prose.

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 resource (French company legal status) and enumerates the two data sources it merges: Sirene administrative status (active/ceased, closure date, legal form, NAF, head office) and BODACC collective proceedings. An agent can distinguish this from a generic company lookup by the insolvency/risk component. It stops short of naming which sibling to prefer, so it is clear but not fully differentiated.

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

Usage Guidelines3/5

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

Usage is only implied by the described content: reach for this when you need legal status plus insolvency proceedings rather than plain registry data. There is no explicit when-to-use, when-not-to-use, or pointer to alternatives such as fr_company, bodacc_health or kyb_check_fr, which plausibly overlap. The only explicit conditional is the payment requirement.

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