Skip to main content
Glama

Search companies by name

search_companies
Read-onlyIdempotent

Find companies by name or name fragment across European business registries and return ranked candidates with registry ID, country, legal form, and status. Use when you know only a company name.

Instructions

Find companies by name (or name fragment) across the pan-European dataset. Returns ranked candidates with registry identifier, country, legal form and status. Use this FIRST when you only know a name; then pass the identifier + country to lookup_company or company_brief. Do not use it to filter by industry or size — that is advanced_search.

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
limitNoMax results (default 10).
queryYesCompany name or fragment.
countryNoISO 3166-1 alpha-2 country of the register (e.g. SK, CZ, AT, PL). Strongly recommended: registry numbers are NOT unique across countries (an SK and a CZ company can share the same 8-digit IČO), and without it the server picks one by tie-break.

Output Schema

NameRequiredDescriptionDefault
dataNoArray of candidate companies, best match first.
metaNoRequest metadata: request_id (quote it in support requests), duration_ms, cached.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed11 schema fields changedv0.2.2
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • removedInput schema / properties / active_only
      Removed value: -{
      -  "description": "If true (default), only active (non-terminated) companies",
      -  "type": "boolean"
      -}
    • changedInput schema / properties / country / description
      Previous value: -"ISO 3166-1 alpha-2 country code filter (e.g. 'SK', 'CZ', 'AT'). Case-insensitive."New value: +"ISO 3166-1 alpha-2 country of the register (e.g. SK, CZ, AT, PL). Strongly recommended: registry numbers are NOT unique across countries (an SK and a CZ company can share the same 8-digit IČO), and without it the server picks one by tie-break."
    • removedInput schema / properties / country / maxLength
      Removed value: -2
    • removedInput schema / properties / country / minLength
      Removed value: -2
    • addedInput schema / properties / country / pattern
      Added value: +"^[A-Za-z]{2}$"
    • changedInput schema / properties / limit / description
      Previous value: -"Max results to return (default 10)"New value: +"Max results (default 10)."
    • removedInput schema / properties / q
      Removed value: -{
      -  "description": "Search query (company name, partial name, address, IČO)",
      -  "maxLength": 200,
      -  "minLength": 1,
      -  "type": "string"
      -}
    • addedInput schema / properties / query
      Added value: +{
      +  "description": "Company name or fragment.",
      +  "maxLength": 200,
      +  "minLength": 2,
      +  "type": "string"
      +}
    • changedInput schema / required
      Previous value: -[
      -  "q"
      -]New value: +[
      +  "query"
      +]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "data": {
      +      "description": "Array of candidate companies, best match first."
      +    },
      +    "meta": {
      +      "description": "Request metadata: request_id (quote it in support requests), duration_ms, cached.",
      +      "type": "object"
      +    }
      +  },
      +  "type": "object"
      +}
  2. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false and destructiveHint=false, so the safety profile is fully covered. The description adds useful behavioral context beyond that: results are ranked candidates rather than exact matches, and the output carries registry identifier, country, legal form and status. It omits paging/ordering caveats, so it is strong but not exhaustive.

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 sentences, each earning its place: purpose, return shape, then workflow routing with an explicit exclusion. Front-loaded with the verb and resource, nothing redundant.

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?

An output schema exists so return values need not be enumerated, and annotations carry the safety profile; the description still supplies the workflow position (first step, hand-off to lookup_company/company_brief) and the boundary against advanced_search. Nothing an agent needs to call this correctly is 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 100%, so query, limit and country are all documented in the schema itself, including the tie-break rationale for country. The description only echoes 'name (or name fragment)' and alludes to carrying country forward, adding little syntax or format meaning beyond the schema. Baseline 3 is appropriate.

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 companies by name'), names the scope ('pan-European dataset'), and previews the payload (registry identifier, country, legal form, status). It is immediately distinguishable from siblings like get_company_details or list_rankings.

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?

Explicit routing: use this FIRST when only a name is known, then feed the identifier + country into lookup_company or company_brief. It also states the negative case — do not use it to filter by industry or size, use advanced_search instead. Both the trigger and the excluded alternatives are named.

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