Skip to main content
Glama

Registry Pages

Search French companies by name

search_french_companies
Read-only

Find French companies (legal entities) by name, optionally with the town. Returns at most 10 matches with SIREN, status and page URL. Use get_french_company for details.

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": {
      "query": "<query>"
    },
    "name": "search_french_companies"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesCompany name, for example "renault lyon"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Beyond the readOnlyHint/openWorldHint annotations, the description discloses the result cap ('at most 10 matches') and the returned fields (SIREN, status, page URL), which matters for deciding whether one call is enough. It does not say what happens on zero matches or whether matching is prefix/fuzzy, leaving a small gap.

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?

Three short sentences: purpose and scope first, result shape second, sibling routing last. Nothing is repeated and no sentence could be dropped without losing information.

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

Completeness5/5

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

For a one-parameter search tool with annotations and no output schema, the description covers what it searches, the result limit, the fields returned, and where to go for full details. An agent has everything needed to call it correctly and interpret the response.

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?

With a single parameter at 100% schema coverage and an example ('renault lyon'), the schema already carries the semantics. The description's 'optionally with the town' confirms that the town is embedded in the same query string rather than being a separate argument, which is a modest clarification rather than new meaning.

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 (legal entities) by name') and scopes it to a country and entity type, which separates it from the Norwegian/UK search siblings. It also names the follow-up tool, so an agent can tell it apart from get_french_company 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly routes the agent: use this to search by name, then 'Use get_french_company for details.' That is a clear alternative with a stated condition. It lacks an explicit when-not-to-use case (e.g., lookup by SIREN directly), but the search-vs-detail split is unambiguous.

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