Skip to main content
Glama
Sirenic MCP server

Sirenic MCP server

Official

Detect company identifiers in text (free)

detect_company_identifiers
Read-only

Scan pasted text to detect French/EU company identifiers—SIREN, SIRET, EU VAT, LEI—with validation and the recommended Sirenic verification call and price.

Instructions

FREE. Paste any text (email, invoice, contract, web page) and detect French/EU company identifiers: SIREN, SIRET (Luhn-checked), EU VAT numbers, LEI (ISO 17442 checksum), each with the recommended Sirenic call and its price. Use this FIRST whenever a company appears in your workflow (customer onboarding, prospect list, supplier invoice, due diligence) to know exactly what to verify and what it costs. Deterministic pattern matching; the text is never stored or logged.

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": {
      "texte": "<texte>"
    },
    "name": "detect_company_identifiers"
  }
}

Input Schema

NameRequiredDescriptionDefault
texteYesRaw text to scan (max 10,000 chars)

Output Schema

NameRequiredDescriptionDefault
hintNoHow to settle the quote, present when payment_required is true.
quoteNoThe signable x402 payment requirements when payment_required is true: {x402Version, accepts[]} where each entry carries scheme, network, amount, asset and payTo (USDC and EURC options at the same numeric amount). Sign one entry and call again with `x_payment`.
resultatNoThe endpoint's JSON response when payment_required is false. Paid responses carry `source`, `disclaimer` and an Ed25519 signature, and every paid JSON response carries a `provenance` array (all tools since 2026-09-06): one entry per block served, with the official register, licence, version, `empreinte_sha256` (full snapshots), `as_of` date and `precision_as_of` (what that date means), plus the common per-block envelope: `etat` in a closed list (servi, absence_mesuree, absence_non_conclusive, partiel, perime, indisponible, sans_objet), `motif` when unavailable, `age_jours` (only for publication or ingestion dates), `couverture` (complete / partielle / non_mesurable with its measure) and `confiance` in bands (faible / moyenne / forte, only where a measure grounds it, never averaged across blocks). Read the states before the numbers: an absence_non_conclusive, indisponible or partiel block is never « nothing to report »; only absence_mesuree asserts an absence. Register codes: GET /v1/provenance/registres ; states, closed lists and reading rules: GET /v1/lecture (both free). The PDF tools carry no JSON envelope (the PDF report prints it).
free_tierNoFree API key offer for this tool, present with a quote.
payment_requiredYesTrue when this response is an x402 payment quote instead of data: settle one of the quote's `accepts` options and call the tool again with `x_payment`.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond the readOnlyHint/openWorldHint annotations: it discloses that matching is deterministic, that checksums are actually validated (Luhn, ISO 17442), that the output includes the recommended next call and its price, and that text is never stored or logged. That privacy guarantee is exactly the kind of context an agent needs before pasting sensitive text.

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 'FREE.' and organized around purpose, usage, and behavior in three tight sentences. Slightly dense with parenthetical lists, but no sentence is wasted.

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?

An output schema exists, so return values needn't be explained, and the annotations cover the safety profile. Combined with the privacy, determinism, and cost-signaling details, an agent has everything needed to call this correctly as a first step.

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% and the single parameter is documented, but the description adds useful meaning by naming the kinds of input to paste (email, invoice, contract, web page). The 10,000-char limit is left to the schema, so it adds value without fully duplicating.

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 (detect) and resource (French/EU company identifiers), then enumerates the identifier types (SIREN, SIRET, EU VAT, LEI) with their validation methods. It is clearly distinguishable from siblings like validate_eu_vat_number or verify_french_invoice, which each target a single identifier rather than scanning free text for all of them.

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

Usage Guidelines4/5

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

Explicitly says 'Use this FIRST whenever a company appears in your workflow' and lists concrete scenarios (onboarding, prospect list, supplier invoice, due diligence). It implies the downstream path ('each with the recommended Sirenic call') but does not name specific sibling tools as alternatives, so it falls short of a 5.

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

Deploy Server

Other Tools