Skip to main content
Glama
bormeapi

BORME MCP Server

by bormeapi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Search companies by name

search_companies
Read-onlyIdempotent

Search Spanish companies by name, including former names and variants, and get ranked company cards to identify the right entity before checking its history, NIF, or brand owner.

Instructions

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.

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. Changed5 schema fields changedv2.1.1
    • changedInput schema / properties / limit / description
      Previous value: -"Cards per page, 1-50 (default 10)."New value: +"Cards per page, integer 1-50, e.g. 5 (default 10)."
    • changedInput schema / properties / name / description
      Previous value: -"Company name or part of it, at least 3 letters or digits; accents, case, punctuation and legal form are ignored."New value: +"The 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."
    • changedInput schema / properties / offset / description
      Previous value: -"Cards to skip. At most 200 cards are ranked; truncated true means more candidates existed, so add another word from the name."New value: +"Cards 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."
    • changedInput schema / properties / province / description
      Previous value: -"The company's province, accent-insensitive, e.g. MADRID, VIZCAYA, or an autonomous community for all of its provinces, e.g. Catalonia; several values can be 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."New value: +"Optional 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."
    • changedInput schema / properties / status / description
      Previous value: -"One of active, dissolved, extinct, sheet_closed; applied like province."New value: +"Optional, one of active, dissolved, extinct, sheet_closed, e.g. active; applied like province."
  2. Addedv1.1.1

TDQS

A4.4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, closed-world and non-destructive, so the safety profile is covered. The description goes well beyond that with free-plan caps (5 cards, hidden_by_plan counting), plan-gated NIF data, ranking order and the 'empty answer is not proof' caveat — but it omits rate-limit/error behavior beyond 'one request per call'. Wait — reassessing: the plan gating, ranking criteria and empty-result caveat are exactly the kind of non-obvious context annotations cannot express, so the score should reflect that added value.

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 in the first two sentences, then matching rules, then result shape and plan caveats. Dense but every clause carries information; the inline JSON return-shape block is the only part bordering on verbose.

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 5-param search tool with no output schema, the description supplies the return shape, ranking logic, plan-driven truncation behavior, match-type interpretation and the failure caveat. An agent can call it and interpret the response correctly without further context.

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 100%, so the baseline is 3. The description still adds meaning the schema does not: match values are 'a lead, not an identification', ranking order (match, active, newest act), and the semantics of truncated. The hidden_by_plan / NIF-plan notes sit outside the parameters but explain result shape, not parameter use.

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 Spanish companies by name and return ranked company cards') and explicitly distinguishes itself from company_history, company_by_nif and brand_owner by naming each sibling and the input that routes to it.

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') plus three named alternatives with the exact condition selecting each (slug, tax ID, brand). No inference required.

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

Deploy Server

Other Tools