Skip to main content
Glama

Find a brand's company

brand_owner
Read-onlyIdempotent

Find the Spanish company a trademark or trading name is linked to, in the Spanish patent office (OEPM) records we hold (since 1987).

Use it when the user names a brand; for a company's own name use search_companies, for a known company's brands use company_brands.

Returns JSON {found, brand, matches: [{brand, kind, company_slug, company_name, company_status, file}], truncated, source, note}: one match per company and name; file is that name's newest OEPM file. kind commercial_name identifies a business; trademark distinguishes goods or services (NESCAFÉ is not another name for Nestlé): say which kind a hit is. Links are holder-name matches (no tax IDs are published); ambiguous holders stay unlinked: present a hit as a name match, not confirmed ownership. found false is not proof the brand is unused. On a hit, use company_history with the slug.

Read-only; one request per call. Needs the basic plan or higher: send your API key in the X-API-Key header (https://bormeapi.com/account).

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

Input Schema

NameRequiredDescriptionDefault
brandYesBrand or trading name, or part of it, at least 3 letters or digits after punctuation is removed, case-insensitive, e.g. "ZARA".
limitNoMaximum matches, integer 1-200, e.g. 10 (default 20).

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 cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description adds substantive context beyond them: holder-name matching with no tax IDs, ambiguous holders left unlinked, 'found false is not proof the brand is unused', the distinction between commercial_name and trademark kinds, one match per company/name, and that file is the newest OEPM file. It also discloses the auth requirement (basic plan or higher, X-API-Key header) and the one-request-per-call limit.

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 come first, then return shape, then caveats, then auth — good front-loading. The enumerated JSON field list is long, but it substitutes for the absent output schema, so most of it earns its place; a few clauses (e.g. the NESCAFÉ aside) are illustrative rather than load-bearing.

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 carries the return contract: field names, the one-match-per-company/name rule, truncation and source fields, and interpretation caveats. Auth, rate (one request per call), and the natural next tool are all present, so nothing an agent needs to call it 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% and the brand/limit descriptions already explain the 3-character rule and the 1-200 range, so baseline 3 applies. The description adds only indirectly, via 'one match per company and name', which hints at how limit is consumed, but it gives no direct parameter syntax or format detail.

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?

Specific verb 'Find' plus a precisely scoped resource: the Spanish company linked to a trademark or trading name in OEPM records since 1987. It explicitly carves itself out from search_companies (company's own name) and company_brands (a known company's brands), so an agent can route 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 Guidelines5/5

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

States the triggering condition ('when the user names a brand'), names the two alternative tools and the conditions that select them, and gives a follow-up step ('On a hit, use company_history with the slug'). Both when-to-use and when-not-to-use are covered.

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.