Skip to main content
Glama

Vérif Entreprise FR

by app.railway.up.api-production-24833
OverviewDiscussionsAdmin

Vérifier une entreprise française (SIREN)

verifier_entreprise
Read-onlyIdempotent

Verify a French company (KYB / supplier check) when you already have its 9-digit SIREN. Returns legal identity (with the intra-EU VAT number and whether VIES reports it active), active/closed status, age, headcount band, establishments, the current insolvency-procedure state parsed from BODACC notices (safeguard, receivership, liquidation, plans, closures), RGE/Qualiopi labels, and a verdict (favorable | vigilance | defavorable | indetermine) justified by stable signal codes, each with its source and a link to the official notice. When to use another tool: if you only know the company name, call rechercher_entreprise first to get the SIREN. This tool only says whether the company holds an RGE label; for the detailed RGE certifications of one establishment (domains, certifying body, validity dates), call qualifications_rge with its SIRET (entreprise.siege.siret in this result). Optional nom: checks whether a name matches the official one (exacte | partielle | aucune) without ever returning the official name — useful for sole traders, whose names are never disclosed. Errors (never charged): an invalid SIREN (wrong length or Luhn key) is rejected before any payment request; an unknown or non-public company returns an error after the payment is verified but before it is settled; if BODACC is unreachable the verdict is indetermine with confidence partielle. Payment: $0.01 per call via x402 (USDC on Base or Solana). No account or API key.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nomNoOptional name to check against the official name (2 to 100 characters).
sirenYes9-digit SIREN of the company (Luhn-valid). Spaces, dots and dashes are accepted.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / nom / description
      Previous value: -"Nom à vérifier (facultatif)."New value: +"Optional name to check against the official name (2 to 100 characters)."
    • changedInput schema / properties / siren / description
      Previous value: -"SIREN, 9 chiffres (clé de Luhn valide)."New value: +"9-digit SIREN of the company (Luhn-valid). Spaces, dots and dashes are accepted."
  2. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds substantial behavior: x402 payment ($0.01 via USDC), billing semantics (invalid SIREN rejected before payment; unknown company fails after verification but before settlement; BODACC unreachable yields verdict=indetermine with confidence partielle). This far exceeds annotation coverage, though a 5 is reserved for even deeper operational context.

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?

Front-loaded with purpose and return contents, then routing, then errors, then payment. Long but dense and well ordered; each sentence carries distinct information, with only marginal overlap in the return enumeration.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description carries the return-value burden and does so fully (identity, VAT/VIES, status, headcount, establishments, insolvency state, labels, verdict with source codes and notice links). Payment, error, and degradation behavior are all covered.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the parameter syntax is already documented. The description still adds meaning: `nom` performs a match check (exacte/partielle/aucune) and never returns the official name, which is useful for sole traders. That is genuine semantic value beyond the schema's length constraint.

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 (verify a French company by its 9-digit SIREN) and enumerates the returned data (legal identity, VAT/VIES, insolvency state, labels, verdict). It explicitly distinguishes itself from both siblings: rechercher_entreprise when only the name is known, qualifications_rge for detailed RGE certifications.

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

Usage Guidelines5/5

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

Gives explicit when-to-use routing ('if you only know the company name, call rechercher_entreprise first'), when to escalate to qualifications_rge, and the precondition of having a valid SIREN. It also covers error conditions, so the agent knows the boundaries of a successful call.

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

All Vérif Entreprise FR 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