Skip to main content
Glama

Get a French company's profile

get_company
Read-onlyIdempotent

Use this when you know a company's SIREN and the user wants its identity, or wants to pre-fill a business customer's onboarding form: name, active or ceased, legal form code, NAF code, creation date, head office, establishments, share capital and current officers (name and role only), with sources and update date. Do not use for financial statements, beneficial owners, contact details or people searches, or as a regulatory identity check (KYC); that data is not provided.

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_company"
  }
}

Input Schema

NameRequiredDescriptionDefault
sirenYesFrench company identifier: 9 digits (spaces allowed).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/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 closed-world, so the safety profile is covered. The description adds meaningful scope context beyond that: officers are returned 'name and role only', results carry sources and an update date, and the data is explicitly not a regulatory KYC check. It stops short of describing result size or pagination, so not a 5.

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?

Two sentences: the positive case with its field inventory first, then the exclusions. The long field list is load-bearing because it tells the agent which user intents this tool answers, and 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?

With no output schema, the description carries the return-value burden and does so by enumerating the profile fields plus provenance and freshness metadata. Combined with the explicit exclusions, an agent has everything needed to decide and call correctly.

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

Parameters3/5

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

There is one parameter and the schema documents it fully (9 digits, spaces allowed, 9-15 length), so the schema does the heavy lifting. The description only reinforces that the SIREN must already be known, adding no format or edge-case detail beyond 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?

Specific verb (get) plus resource (French company profile keyed by SIREN), with an explicit enumeration of the returned fields: identity, active/ceased status, legal form, NAF code, creation date, head office, establishments, share capital and officers. An agent can distinguish this from search_companies or get_establishment purely from the description.

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?

States the precondition ('when you know a company's SIREN') and two concrete use cases (identity lookup, pre-filling onboarding forms), then names explicit exclusions: financial statements, beneficial owners, contact details, people searches, and KYC. Both the when and the when-not are present.

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.