Skip to main content
Glama

company-search

Search French companies by name or SIREN to get identity, activity, and status details, then use the SIREN to request a full company profile.

Instructions

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, 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: -{
      -  "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"
      -]
  2. First observedv1.1.4

TDQS

A4.2/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden. It usefully discloses cost and payment rail ("$0.020 per call, x402/USDC"), which is genuine behavioral context an agent needs. However it says nothing about match behavior (exact vs fuzzy), result limits, pagination, or error cases — significant gaps for a search endpoint with no annotation coverage.

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-loads the resource and routes to next steps well, but "find French companies by name or SIREN" is repeated almost verbatim in the usage sentence. The bracketed pricing tag is placed last, which is fine, but the em-dash stacking makes it feel more like marketing copy than a spec.

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 and no annotations, the definition covers purpose, sequencing, input, and cost — enough to call it correctly. The remaining gap is what the response actually contains beyond the three words "identity, activity, status," and whether results are limited or ranked.

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 itself only says "query parameters, e.g. {q: 'Paris'}". The description adds real meaning by naming the parameter explicitly ("?q=name") and clarifying it accepts a name or a SIREN, which the schema never states.

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 enumerates what is returned ("identity, activity, status"). It also positions itself as "the entry point to the company funnel," which separates it from company-profile in the sibling set.

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 describes 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." Both the when-to-use condition and the named next-step alternative are given, leaving little to inference.

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