Skip to main content
Glama

company-profile

Fetch consolidated French company registry identity by SIREN—legal form, NAF, headcount, HQ, VAT, creation date, and status—to verify a business and assess its standing.

Instructions

Xynaptic Company Profile — consolidated identity from the French state registry: SIREN, legal form, NAF, headcount, HQ, VAT, creation, status. Parameter: ?siren=. Usage: Use with a SIREN from company-search for registry identity, status and financial strength of a French company. [price: $0.020 per call, x402/USDC]

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": {
      "params": "<params>"
    },
    "name": "company-profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
paramsYesquery parameters, e.g. {q: 'Paris'}

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.2.2
    • changedInput schema / properties / params / description
      Previous value: -"query parameters"New value: +"query parameters, e.g. {q: 'Paris'}"
    • removedInput schema / properties / params / properties
      Removed value: -{
      -  "naf": {
      -    "description": "example: \"70.10Z\"",
      -    "type": "string"
      -  },
      -  "name": {
      -    "description": "example: \"DANONE\"",
      -    "type": "string"
      -  },
      -  "siren": {
      -    "description": "required. example: \"552032534\"",
      -    "type": "string"
      -  },
      -  "status": {
      -    "description": "example: \"active\"",
      -    "type": "string"
      -  }
      -}
    • removedInput schema / properties / params / required
      Removed value: -[
      -  "siren"
      -]
  2. First observedv1.1.4

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description does carry the burden, and it does add real value by disclosing the cost model ('$0.020 per call, x402/USDC') and the upstream data source. However, it says nothing about lookup behavior on invalid SIRENs, whether the result is cached, or what the response structure looks like, which matters for a paid call.

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?

The identity and returned fields are front-loaded, with usage and pricing trailing — a sensible ordering. The dense abbreviation cluster (SIREN, NAF, VAT, HQ) is compact but still readable; no sentence is clearly wasted.

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?

For a single-parameter lookup with no output schema, the description supplies the source registry, the returned fields, the parameter name, the upstream sibling, and the price — enough to call it correctly. The absence of any error or empty-result behavior keeps it short of complete.

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?

The schema is nominally 100% covered but its only guidance is a misleading generic example '{q: 'Paris'}'. The description corrects this by naming the actual parameter '?siren=', which is genuine meaning added beyond the schema rather than a restatement.

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 the resource (French state registry company identity) and enumerates the concrete fields returned: SIREN, legal form, NAF, headcount, HQ, VAT, creation, status. That is specific enough to distinguish it from the generic sibling company-search, though it lacks an explicit verb and the field list carries most of the differentiation weight.

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?

It explicitly states the prerequisite source ('Use with a SIREN from company-search') and the intended purpose (registry identity, status, financial strength), which effectively chains it to the sibling. It does not say when NOT to use it or what happens if the SIREN is unknown, 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.