Skip to main content
Glama

Search French companies and establishments in the official

b2b_france_annuaire_entreprises
Read-only

Search French companies and establishments in the official Annuaire des Entreprises (SIRENE data): SIREN, full name, head-office address, main activity code (NAF) and active state. Public register data only; no financial statements. Price: $0.002 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

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": {
      "q": "<q>"
    },
    "name": "b2b_france_annuaire_entreprises"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYesCompany name or SIREN, 2 to 100 characters
limitNoMax results, 1 to 25 (default 10)

Output Schema

NameRequiredDescriptionDefault
qNo
countNo
sourceNo
checkedAtNo
companiesNo
totalResultsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered; the description adds genuinely new operational context that annotations cannot convey: pay-per-call pricing ($0.002), the x402/USDC payment mechanism, and the fact that failed calls are free. It also constrains data scope to the public register. Minor gaps remain (pagination behavior, error semantics), but the added transparency is substantial.

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 sentences, front-loaded with the core purpose before scope and pricing. Dense but every clause carries information; the pricing sentence is long but justified because cost is decision-relevant. Slight tightening of the payment-network enumeration would be possible.

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 two-parameter read-only lookup with a full schema and an output schema, the description covers purpose, data scope, exclusions, and cost. Return values need not be explained given the output schema, though they are helpfully summarized. Missing only minor operational detail such as result pagination or match-quality 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 both q and limit are already documented in the schema. The description reinforces that the query accepts SIREN or company name, matching the schema's 'Company name or SIREN' wording, but adds no new syntax, matching behavior, or format detail beyond it. Baseline 3 applies.

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 a specific verb and resource ('Search French companies and establishments') and names the authoritative source (Annuaire des Entreprises / SIRENE), plus enumerates the returned fields (SIREN, name, head-office address, NAF, active state). An agent can distinguish this from other business-registry siblings such as b2b_netherlands_kvk or b2b_guidestar by jurisdiction and by the explicit 'no financial statements' boundary.

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 implied by the scope statements ('French companies', 'Public register data only; no financial statements'), which tells the agent when this tool is inapplicable. However, there is no explicit when-to-use framing and no named alternative for financial data or non-French entities, leaving routing to inference.

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