Skip to main content
Glama

mcp.xynaptic

company-profile

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / params / description
      Previous value: -"query parameters, e.g. {q: 'Paris'}"New value: +"query parameters"
    • addedInput schema / properties / params / properties
      Added value: +{
      +  "company": {
      +    "description": "example: {\"siren\":\"552032534\",\"name\":\"DANONE\",\"sigle\":null,\"legal_form\":\"5599\",\"naf\":\"70.",
      +    "type": "string"
      +  },
      +  "establishments": {
      +    "description": "example: {\"total\":19,\"open\":3}",
      +    "type": "string"
      +  },
      +  "identity": {
      +    "description": "example: {\"status\":\"active\",\"created\":\"1955-01-01\",\"closed\":null,\"vat\":\"FR27552032534\",\"i",
      +    "type": "string"
      +  },
      +  "location": {
      +    "description": "example: {\"hq_city\":\"PARIS\",\"hq_postcode\":\"75009\",\"hq_address\":\"59 RUE LA FAYETTE\"}",
      +    "type": "string"
      +  },
      +  "officers_count": {
      +    "description": "example: 13",
      +    "type": "number"
      +  }
      +}
    • addedInput schema / properties / params / required
      Added value: +[]
  2. Changed3 schema fields changed
    • 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"
      -]
  3. Changed3 schema fields changed
    • changedInput schema / properties / params / properties / siren / description
      Previous value: -"example: \"552032534\""New value: +"required. example: \"552032534\""
    • addedInput schema / properties / params / required
      Added value: +[
      +  "siren"
      +]
    • changedInput schema / required
      Previous value: -[]New value: +[
      +  "params"
      +]
  4. Changed4 schema fields changed
    • removedInput schema / properties / body
      Removed value: -{
      -  "description": "JSON body for POST endpoints (e.g. insurance, ai-chat, production-risk)",
      -  "type": "object"
      -}
    • changedInput schema / properties / params / description
      Previous value: -"query parameters, e.g. {city: 'Paris', type: 'Appartement'}"New value: +"query parameters"
    • addedInput schema / properties / params / properties
      Added value: +{
      +  "naf": {
      +    "description": "example: \"70.10Z\"",
      +    "type": "string"
      +  },
      +  "name": {
      +    "description": "example: \"DANONE\"",
      +    "type": "string"
      +  },
      +  "siren": {
      +    "description": "example: \"552032534\"",
      +    "type": "string"
      +  },
      +  "status": {
      +    "description": "example: \"active\"",
      +    "type": "string"
      +  }
      +}
    • addedInput schema / required
      Added value: +[]
  5. First observed

TDQS

A4.2/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses the data source (French state registry), the consolidated field set, and the pricing/payment model ($0.020 per call, x402/USDC), but it does not describe response format, freshness, error behavior, or constraints beyond the SIREN input.

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?

The description is compact and front-loaded: it names the resource, lists the important fields, identifies the parameter, states the usage dependency, and gives cost/payment information without extraneous prose.

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 simple single-parameter lookup with no output schema and no annotations, the description provides enough context to understand the source, input, and high-level returned fields. It could be stronger by clarifying the actual response shape and by not implying 'financial strength' beyond the fields listed.

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 nominally 100%, but the schema properties look like example output fields rather than a clear input contract. The description compensates by explicitly identifying the input as ?siren=, which is the key semantic detail an agent needs to invoke the tool correctly.

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?

The description states a specific resource and scope: a consolidated French company registry profile covering SIREN, legal form, NAF, headcount, HQ, VAT, creation date, and status. It clearly distinguishes this lookup from the sibling company-search by positioning it as the registry identity/status view for a known SIREN.

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 says to use a SIREN obtained from company-search and identifies the intended use case: registry identity, status, and financial strength. It does not state when not to use the tool or clarify that 'financial strength' may not actually be present in the listed fields, so it falls short of full alternative/exclusion guidance.

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