open-data-mcp

dataandbeyond--france-company-search

Read-only

Search French companies by name, SIREN, or SIRET using official Sirene data; filter by NAF code or postal code and get computed VAT numbers.

Instructions

French companies by name, SIREN or SIRET (Sirene / Recherche d'entreprises), with computed VAT number. Calls the official API directly.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "dataandbeyond--france-company-search"
  }
}

Input Schema

Name	Required	Description
`nafCode`	No	e.g. 62.01Z
`queries`	No	Names, SIREN (9 digits) or SIRET (14 digits). Example values: ["Danone","552032534"]
`waitSecs`	No	Max seconds (0–45, default 30) to cap the wait for the Actor run to reach terminal state. For long-running Actors the response returns at the cap with the current run status; follow `nextStep` to poll via get-actor-run. Set to 0 to fire-and-forget.
`onlyActive`	No	Only active companies Example values: true
`postalCode`	No	Optional.
`maxResultsPerQuery`	No	Max matches per query Example values: 3

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.0Oct 30, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds that it calls the official API directly (data provenance), which is useful, but says nothing about rate limits, quotas, or the waitSecs polling behavior beyond what the schema documents.

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 short sentences with no filler, and the resource/identifier scope is front-loaded. It is efficient, though it stops just short of routing information an agent would want.

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 lookup tool with fully documented parameters and no output schema, the description covers the resource, accepted identifiers, and the computed VAT output. It is missing only usage routing and any mention of result-set behavior.

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 all six parameters (nafCode, queries, waitSecs, onlyActive, postalCode, maxResultsPerQuery) are already documented in the schema. The description adds no parameter-level meaning, 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?

States the resource (French companies) and identifier types (name, SIREN, SIRET), plus the source (Sirene / Recherche d'entreprises) and a value-add (computed VAT number). Sibling country-specificity (vs nordic-company-registry, eu-company-verify) lets an agent pick the France tool, though the verb 'search' is only implied.

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?

No explicit when-to-use or when-not guidance, and no alternative named. The scope word 'French' implicitly differentiates from the Nordic registry and eu-company-verify, but the agent must infer that rather than being told.

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

Deploy Server