mcp.xynaptic

company-search

Xynaptic Company Search — find French companies by name or SIREN: identity, activity, status. The entry point to the company funnel. Parameter: ?q=name. Usage: First step of the French company funnel: find a company by name or SIREN, get its SIREN, then call company-profile for the full dossier. [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 / query / description
```
Previous value: -"example: \"michelin\""New value: +"required. example: \"michelin\""
```
- addedInput schema / properties / params / required
```
Added value: +[
+  "q"
+]
```
- 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: +{
+  "query": {
+    "description": "example: \"michelin\"",
+    "type": "string"
+  },
+  "results": {
+    "description": "example: 3",
+    "type": "number"
+  },
+  "top": {
+    "description": "example: {\"siren\":\"424622884\",\"name\":\"MICHELIN\"}",
+    "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 does add a genuinely useful behavioral trait absent from structured fields — the cost and payment mechanism ('$0.020 per call, x402/USDC'). However, it discloses nothing about auth requirements, rate limits, or the shape of results beyond three field labels, so gaps remain for a no-annotation tool.

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

Conciseness3/5

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

Front-loaded and reasonably short, but 'find a company by name or SIREN' is stated twice and the 'funnel' framing is repeated in both the positioning and usage sentences. Some redundancy that does not earn its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema and no annotations, the description should carry more. It names three result fields and the cost, but gives no return structure, result count semantics, or auth context. Adequate for routing, incomplete for invocation confidence.

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 adds a syntax hint ('Parameter: ?q=name'), but the schema's own properties are top/query/results with a required 'q' — the description does not clarify this naming mismatch or explain top/results, so it adds only marginal value.

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 verb and resource (find French companies) and the fields surfaced (identity, activity, status), and distinguishes itself from the sibling company-profile by positioning itself as the entry point. An agent can tell it apart from company-profile without opening either schema.

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?

Explicitly names the workflow: 'First step of the French company funnel: find a company by name or SIREN, get its SIREN, then call company-profile for the full dossier.' The when-to-use condition and the follow-up alternative are both stated, leaving nothing to inference.

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?