Skip to main content
Glama

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]

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

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: +{
      +  "agent": {
      +    "description": "example: {\"actionability\":\"high\",\"recommended_actions\":[\"get_company_profile\",\"check_offi",
      +    "type": "string"
      +  },
      +  "facts": {
      +    "description": "example: {\"total_results\":10000,\"returned\":10,\"companies\":[{},{}]}",
      +    "type": "string"
      +  },
      +  "query": {
      +    "description": "required. example: \"carrefour\"",
      +    "type": "string"
      +  }
      +}
    • addedInput schema / properties / params / required
      Added value: +[
      +  "q"
      +]
  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: -{
      -  "query": {
      -    "description": "required. example: \"michelin\"",
      -    "type": "string"
      -  },
      -  "results": {
      -    "description": "example: 3",
      -    "type": "number"
      -  },
      -  "top": {
      -    "description": "example: {\"siren\":\"424622884\",\"name\":\"MICHELIN\"}",
      -    "type": "string"
      -  }
      -}
    • removedInput schema / properties / params / required
      Removed value: -[
      -  "q"
      -]
  3. Changed3 schema fields changed
    • 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"
      +]
  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: +{
      +  "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: +[]
  5. First observed

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose non-schema behavior: the per-call price of $0.020 and the x402/USDC payment requirement, plus the funnel sequencing. It omits result limits/pagination behavior and error handling, which matters for a search that can return large result sets.

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 scannable, but it repeats itself: 'find French companies by name or SIREN' and 'find a company by name or SIREN' say the same thing, as do 'The entry point to the company funnel' and 'First step of the French company funnel'. Tightening would cut nearly a sentence without losing information.

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?

No output schema exists, so the description must and does convey what comes back (identity, activity, status) along with cost and next-step routing, which is sufficient for a one-parameter search. The main remaining gap is result-volume behavior, hinted at only by the schema example showing total_results 10000 versus returned 10.

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 already 100%, so baseline is 3, but the description adds meaning beyond the schema's bare example ('carrefour') by stating that q accepts either a company name or a SIREN. It does not explain the nested agent/facts properties, which are only illustrated in 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?

States a specific verb and resource ('find French companies by name or SIREN') and the fields returned (identity, activity, status). It explicitly positions itself as the entry point relative to the sibling company-profile, so an agent can distinguish the two 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?

Gives explicit step-by-step guidance: this is the first step of the funnel, its job is to yield a SIREN, then the agent should call company-profile for the full dossier. The alternative and the condition selecting it are both named.

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