Skip to main content
Glama

Vérif Entreprise FR

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

Trouver le SIREN d'une entreprise par son nom

rechercher_entreprise
Read-onlyIdempotent

Find a French company's SIREN when you only know its name (3 to 100 characters). Narrow the results with code_postal (5-digit postcode, e.g. 69003) or commune (5-character INSEE commune code, e.g. 69383 — not a city name); both can be combined. Returns at most 10 matches with siren, siret of the establishment matching the location filter (otherwise the head office), name, status, NAF code, city, postcode and creation date. plusDeResultats: true means more companies match: refine the query. No personal data: sole traders appear under their trade name only. Next step: call verifier_entreprise with the SIREN for a full check, or qualifications_rge with the SIRET for RGE certifications. Errors (never charged): a query shorter than 3 characters or a malformed filter is rejected before any payment request. Payment: $0.002 per call via x402 (USDC on Base or Solana). No account or API key.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qYesCompany name or part of it (3 to 100 characters).
communeNoOptional INSEE commune code (5 characters, e.g. 69383 or 2A004), not a city name.
code_postalNoOptional 5-digit French postcode, e.g. 69003.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / code_postal / description
      Added value: +"Optional 5-digit French postcode, e.g. 69003."
    • changedInput schema / properties / commune / description
      Previous value: -"Code commune INSEE."New value: +"Optional INSEE commune code (5 characters, e.g. 69383 or 2A004), not a city name."
    • changedInput schema / properties / q / description
      Previous value: -"Nom de l'entreprise."New value: +"Company name or part of it (3 to 100 characters)."
  2. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), yet the description adds substantial context beyond them: a 10-result cap, the plusDeResultats overflow signal, a no-personal-data policy, error behavior (short queries rejected and never charged), and the x402 payment model with cost.

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?

Dense but front-loaded: the query purpose, filters, and output shape come before payment logistics. It is a long paragraph, and the payment/error sentences could be trimmed, but each sentence carries operational value.

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?

No output schema exists, so the description compensates by enumerating the returned fields (siren, siret, name, status, NAF, city, postcode, creation date) plus the overflow flag. For a 3-parameter paid lookup tool, nothing essential is missing.

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 baseline is 3, but the description earns above it by clarifying that `commune` is an INSEE code and 'not a city name' and that the two filters are combinable — semantics the regex patterns alone would not convey.

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+resource ('Find a French company's SIREN') and the exact condition under which it applies ('when you only know its name'). It is clearly distinct from the sibling tools, which are positioned as downstream steps rather than alternatives.

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?

Explicit context for use, plus named next steps: call verifier_entreprise with the SIREN or qualifications_rge with the SIRET. It also tells the agent how to react to plusDeResultats (refine the query), which is a routing decision.

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