Skip to main content
Glama
bormeapi

BORME MCP Server

by bormeapi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Find a brand's company

brand_owner
Read-onlyIdempotent

Identify the Spanish company linked to a trademark or trading name using OEPM records since 1987. Returns name-matched holders with company status and slug for further registry lookups.

Instructions

Find the Spanish company a trademark or trading name is linked to, in the Spanish patent office's (OEPM) trademark and commercial-name records we hold (the archive starts in 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}. 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 come from holder-name matching (the office publishes no tax IDs); 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).

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. Changed2 schema fields changedv2.1.1
    • changedInput schema / properties / brand / description
      Previous value: -"Brand or trading name, or part of it."New value: +"Brand or trading name, or part of it, at least 3 letters or digits after punctuation is removed, case-insensitive, e.g. \"ZARA\"."
    • changedInput schema / properties / limit / description
      Previous value: -"Maximum results, 1-200 (default 20)."New value: +"Maximum matches, integer 1-200, e.g. 10 (default 20)."
  2. Addedv1.1.1

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already cover read-only/idempotent safety, but the description adds substantial context beyond them: the 1987 archive boundary, that links come from holder-name matching rather than tax IDs, that ambiguous holders remain unlinked, and above all the epistemic caveat that a hit is a name match not confirmed ownership and that found=false is not proof the brand is unused. Auth and plan requirements plus 'one request per call' are also disclosed.

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?

Front-loaded with purpose, then routing, then return shape and caveats, then auth. Dense but nearly every sentence carries decision-relevant information; the return-schema field enumeration is the one segment that runs long for a tool with no output schema.

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 supplies the return JSON shape including truncated, source and note, explains the kind discriminator semantics, and pre-empts the two most likely misinterpretations (name match vs ownership, found=false vs unused). Nothing needed to call or interpret 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 description coverage is 100%, so the schema already documents both the brand string (minimum length, case-insensitivity, partial matching) and the limit range. The description adds no further parameter detail, which is acceptable at full coverage but leaves this at baseline.

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 the Spanish company a trademark or trading name is linked to') and names the exact data source, OEPM trademark and commercial-name records since 1987. It explicitly differentiates itself from two named siblings by input type.

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 trigger ('when the user names a brand') and routes two adjacent cases elsewhere: company's own name to search_companies, known company's brands to company_brands. It also adds a follow-up path ('On a hit, use company_history with the slug'), so the agent knows what to do next.

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