Skip to main content
Glama

Registry Pages

French company by SIREN

get_french_company
Read-only

Official register data (INSEE Sirene) for one French company: name, status, legal form, activity, headcount band, VAT number, head office town, and the page URL to cite.

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": {
      "siren": "<siren>"
    },
    "name": "get_french_company"
  }
}

Input Schema

NameRequiredDescriptionDefault
sirenYes9-digit SIREN, or a 14-digit SIRET

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds genuine context beyond that — the upstream source (INSEE Sirene) and the fact that a citable page URL is returned — but says nothing about not-found handling, error behavior, or whether data can be stale.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with zero filler: source, scope, and returned fields in one pass. The field enumeration earns its space because no output schema exists.

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?

With one parameter and no output schema, the description usefully compensates by listing the returned fields and the citable page URL. What remains missing is behavioral edge cases (unknown SIREN, SIRET-to-SIREN handling) and explicit routing to the search alternative.

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 schema itself documents the 9-digit SIREN / 14-digit SIRET format, so the schema carries the load. The description reinforces the identifier-based lookup but does not add format, validation, or normalization details beyond what the schema already states; 3 would be the baseline, with slight credit for the identifier framing tied to 'one company'.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific resource and scope — 'Official register data (INSEE Sirene) for one French company' — and enumerates the returned attributes, so an agent knows exactly what a call yields. The singular 'one French company' implicitly separates it from the search_french_companies family, though no sibling is named explicitly.

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 only implied: the singular scope and the SIREN key suggest a lookup when an identifier is already known. There is no statement about when to prefer this over search_french_companies or check_french_vat, and no exclusion for cases without a SIREN.

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