Skip to main content
Glama

Search French companies

search_companies
Read-onlyIdempotent

Use this when the user names a French company (or gives a SIREN or SIRET) and you need to identify it: returns up to 20 matches with name, SIREN, status, legal form code, NAF code and head-office city. Name matching is a prefix match on the official name. Do not use for people, officers or shareholders, and do not use it to list companies by sector or area.

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

Input Schema

NameRequiredDescriptionDefault
pageNo
limitNo
queryYesCompany name, SIREN or SIRET.

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?

Annotations already establish read-only, idempotent, non-destructive, and closed-world behavior, while the description adds useful operational context: prefix matching on official names, a maximum of 20 matches, and the fields returned. It does not cover edge cases such as no-match behavior or exact-identifier handling, but it meaningfully extends the annotation profile.

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?

The description is compact and front-loaded: it starts with the trigger condition, then explains results and matching behavior, and closes with exclusions. Every sentence carries actionable information without repetition.

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 simple read-only search tool with no output schema, the description supplies the essential context: accepted identifiers, match behavior, result cap, returned fields, and exclusion boundaries. Nothing critical for correct invocation appears to be missing.

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 coverage is low at 33%, and the description compensates for the main query parameter by explaining that name matching is a prefix match on the official name and that SIREN/SIRET are accepted. However, it adds little about page and limit beyond what the schema already conveys through defaults and bounds.

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?

The description states a specific verb and resource ("search companies") with a clear scope (French companies) and identifies the core use case: identifying a company from a name, SIREN, or SIRET. It also distinguishes the tool from adjacent concepts by excluding people, officers, shareholders, and sector/area listing.

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?

It gives explicit when-to-use guidance (user names a French company or provides SIREN/SIRET and you need to identify it) and clear when-not-to-use exclusions. It does not explicitly route the agent to the closest sibling, such as get_company, so it falls short of fully naming alternatives.

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.