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]

Input Schema

Name	Required	Description	Default
`params`	Yes	query parameters

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 3, 2026
- 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"
+]
```

Changed4 schema fields changedOct 2, 2026

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: +[]
```

First observedOct 1, 2026

TDQS

A3.9/5.0

Behavior3/5

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

No annotations are provided, so the description carries the full burden. It usefully discloses the pricing model ($0.020 per call, x402/USDC) and the returned field set, but says nothing about rate limits, authentication beyond payment, error behavior, or freshness/latency of the registry data.

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?

Dense but front-loaded: resource and field list first, then parameter, usage, and price. Every clause adds information, though the em-dash field enumeration is slightly list-like and could be trimmed without loss.

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?

There is no output schema, so the description appropriately enumerates the identity fields an agent can expect. Combined with the SIREN usage note and pricing, it is complete enough to call correctly, with only error/edge-case behavior left unaddressed.

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?

Schema description coverage is 100%, so the baseline is 3. The description flags the ?siren= parameter and its role as the required lookup key, but does not mention the other documented params (naf, name, status) or clarify that siren must be a 9-digit SIREN rather than a SIRET.

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 resource (consolidated French state-registry company identity) and enumerates the exact fields returned (SIREN, legal form, NAF, headcount, HQ, VAT, creation, status). It explicitly differentiates from the sibling company-search by positioning itself as the downstream identity lookup keyed on a 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?

Provides clear usage context: "Use with a SIREN from company-search for registry identity, status and financial strength of a French company". It names the sibling that produces the input key and states the intent, but gives no explicit when-not-to-use or handling for an invalid/unknown SIREN.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All mcp.xynaptic tools Inspect

Try in Browser

Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?