Skip to main content
Glama

Search companies by name

search_companies
Read-onlyIdempotent

Find Spanish companies by name and return ranked company cards. Use it first when the user gives a company name, then company_history with its company_slug; with a tax ID use company_by_nif, with a brand use brand_owner.

Matches current names, former names and variants, ignoring accents, case, punctuation and the legal form. Returns JSON {query, count, total, total_is_at_least, truncated, limit, offset, companies: [{company_slug, name, legal_form, province, municipality, status, in_insolvency, last_act_date, match, matched_on}]}. match is exact, prefix, contains or fuzzy (a lead, not an identification; say so). Ranked by match, then active companies, then newest act.

Read-only; one request per call; not limited by the free plan's 7 days of history. The free plan shows at most the first 5 ranked cards; hidden_by_plan counts the rest: relay its note. The NIF is on the card from the basic plan up (X-API-Key header). An empty answer is not proof that a business does not exist.

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

Input Schema

NameRequiredDescriptionDefault
nameYesThe bare company name or part of it, at least 3 letters or digits and at most 200 characters, e.g. "inditex" or "Talleres Jarama": no city, parentheses or notes. Matching allows for case, accents and punctuation, and a legal form such as SL or SA can be left out. Do not repeat the same query unchanged after an empty answer: read note and hidden_by_plan if present.
limitNoCards per page, integer 1-50, e.g. 5 (default 10).
offsetNoCards to skip, integer 0-200 (default 0), e.g. 10. At most 200 cards are ranked; truncated true means a candidate cap was reached or a search step ran out of time, so add another word from the name.
statusNoOptional, one of active, dissolved, extinct, sheet_closed, e.g. active; applied like province.
provinceNoOptional province, accent-insensitive, e.g. MADRID or VIZCAYA, or an autonomous community for all of its provinces, e.g. Catalonia; several values separated by commas, e.g. BIZKAIA,GIPUZKOA. Applied to the candidates the search reads (2,000 with a filter), so a broad name can return fewer companies than match it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only cover the safety profile; the description adds matching behavior (accents, case, punctuation, legal form ignored; former names and variants matched), ranking order (match, then active, then newest act), and the meaning of the match field as a lead rather than an identification. It also documents plan-gating behavior (free plan shows only the first 5 cards, hidden_by_plan counts the rest, NIF requires the basic plan with X-API-Key) and one-request-per-call semantics.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose and routing are front-loaded, and the follow-up/alternative routing is compressed into one sentence. The inline JSON return-shape block is dense and duplicates some schema wording, but it earns its place because there is no output schema; minor redundancy with the parameter descriptions keeps it from a 5.

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?

With no output schema, the description fully describes the response envelope and card fields, field semantics, ranking, truncation, and plan-limited visibility. It also covers the caveats an agent needs to avoid wrong conclusions (fuzzy leads, empty results, hidden_by_plan note), which is complete for a 5-parameter search tool.

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 the schema already explains name, limit, offset, status and province in detail, including the 2,000-candidate cap and truncated semantics. The description adds little parameter-specific meaning beyond reinforcing that the name goes in bare and that a broad name can return fewer companies than actually match; baseline 3 applies when the schema does the heavy lifting.

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?

"Find Spanish companies by name and return ranked company cards" states a specific verb, resource and output form. It explicitly separates itself from company_by_nif (tax ID), brand_owner (brand) and company_history (follow-up by slug), so an agent can route without opening any sibling 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 an explicit when-to-use rule ("Use it first when the user gives a company name, then company_history with its company_slug") plus the two alternative routes by tax ID and brand. It also states a negative rule: don't repeat the same query after an empty answer, and treat an empty answer as non-proof of non-existence.

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.