Skip to main content
Glama

Distil — Machine-Native Public Data Refinery

by com.distil-data

Get France Enterprise Filing

get_fr_company_filing
Read-onlyIdempotent

Fetches verified French statutory enterprise dossier from INPI / SIRENE by 9-digit SIREN (< 1.5 KB). Returns official INSEE legal form (SA, SAS, SARL, SE), NAF/APE activity codes, active establishment count, registered headquarters address, and statutory officers/directeurs généraux.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
forceFreshNoSpend Control: When true, bypasses Edge KV cache and forces a real-time statutory primary registry call (applies 2.5x Freshness Inconvenience Surcharge). Default: false.
maxAgeHoursNoSpend Control: Maximum acceptable data age in hours (e.g. 48 for 2 days tolerance). If cache satisfies this, delivers sub-5ms at standard 1.0x Economy rate. Set to 0 to force live primary fetch.
sirenOrQueryYes9-digit French SIREN enterprise number (e.g. '552032534' for L'Oréal, '855200887' for Michelin).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
contentYes
isErrorNo

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, open-world, and non-destructive behavior, so the bar is lower. The description adds useful context beyond annotations: 'verified', official statutory source (INPI / SIRENE), response size cap (<1.5 KB), and the specific official data elements returned.

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?

Two information-dense sentences with the action and scope front-loaded. The return-field list and response-size note are compact and add value; there is no filler or redundancy.

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?

Given the full annotations, complete parameter schema, and existing output schema, the description sufficiently covers source, country, identifier format, and return content. It is nearly complete but does not explicitly mention alternative sibling tools for search or other countries, so it stops just short of maximal completeness.

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%, with all three parameters documented in detail and examples, so the baseline is 3. The description adds little parameter-level meaning beyond restating the 9-digit SIREN format; forceFresh and maxAgeHours are only explained in the schema.

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 an exact action ('Fetches verified French statutory enterprise dossier'), named sources (INPI / SIRENE), required identifier format (9-digit SIREN), and enumerates returned fields. The French scope and SIREN input clearly distinguish it from sibling country-filing and search tools.

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?

The description implies lookup of a specific French company filing when a SIREN is known, but it does not explicitly say when to prefer this over search_fr_companies or the UK/US filing equivalents, nor does it state exclusions. The intended context is clear but left to inference.

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

All Distil — Machine-Native Public Data Refinery toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4/5.0
Disambiguation5/5

Each tool maps to a distinct data product: country-specific filings, tender records/search, risk scoring, sanctions screening, and entity graphs. The search/get split cleanly separates discovery from retrieval, and even similar country-specific tools are clearly qualified by region and entity type.

Naming Consistency5/5

All tools use a consistent snake_case verb_noun pattern: get_* for retrieval and search_* for discovery, with country or region qualifiers where applicable. Cross-cutting tools like get_corporate_risk_score and get_tender_intelligence fit the same pattern without feeling out of place.

Tool Count4/5

At 16 tools, the server is slightly above the ideal 3-15 range, but the multi-country, multi-domain scope justifies nearly every tool. The set is heavier than a tightly focused server, yet no tool feels redundant.

Completeness4/5

The set covers the core read-only workflow well: search to find entities or tenders, get to retrieve records, plus analytical tools for risk, sanctions, and tender intelligence. Minor gaps exist, such as no Spanish company registry access and no UK tender search, but these are workable and do not block primary due-diligence workflows.

Resources