Skip to main content
Glama
Sirenic MCP server

Sirenic MCP server

Official

Suggest French company names (free)

suggest_company_names
Read-only

Autocomplete a French company name to retrieve up to five matching records with SIREN, city, postcode, NAF code, and active/ceased status, then use the SIREN in other registry tools.

Instructions

FREE. French company name autocomplete: type the beginning of a company name and get up to 5 matches with SIREN, city, postcode, NAF code (with its nomenclature, NAF 2025 code and status) and active/ceased status. Use it FIRST to turn a name into the SIREN that every other Sirenic tool takes as input: no account, no API key, no payment. Source: the official INSEE Sirene register (open data), companies and sole traders whose record is publicly diffusible. Matches the START of the name, then whole words; no typo tolerance and no match-confidence score; for those, plus the full profile, use search_french_companies ($0.002) and get_french_company_profile ($0.005).

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": "suggest_company_names"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYesStart of the company name (3 characters minimum once cleaned up), or a 9-digit SIREN; labelled ("SIREN : 552 032 534") is fine.

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.8/5.0
Behavior5/5

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

Annotations only declare readOnlyHint and openWorldHint; the description adds cost (free), auth requirements (no account, no API key, no payment), data provenance (official INSEE Sirene register, publicly diffusible records only) and matching behaviour limits (prefix then whole words, no fuzziness). This is materially more than the annotations provide.

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-loads 'FREE' and the core action, and every clause (pricing, auth, provenance, matching limits, alternatives) carries information. It is a single very dense paragraph, so scanning for the alternative-tool routing takes effort, but there is no filler.

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?

For a one-parameter lookup with an output schema, nothing an agent needs is missing: cost, auth, source, matching behaviour, result fields and escalation paths are all covered. Return-value detail is legitimately delegated to the output schema.

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 adds matching semantics the schema does not state: it matches the START of the name then whole words, and returns up to 5 matches. That meaningfully changes how an agent should phrase the q value, though it does not restate length limits or the SIREN-detection behaviour already in the schema.

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 (French company name autocomplete returning up to 5 matches with SIREN, city, postcode, NAF code and status) and explicitly positions itself against search_french_companies and get_french_company_profile. The agent can distinguish it from siblings without opening a schema.

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 an explicit ordering rule ('Use it FIRST to turn a name into the SIREN that every other Sirenic tool takes as input') plus the exclusion condition: no typo tolerance or match-confidence score, use search_french_companies or get_french_company_profile for those. Both the when and the when-not are stated with named alternatives.

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