Skip to main content
Glama
bormeapi

BORME MCP Server

by bormeapi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

A company's brands

company_brands
Read-onlyIdempotent

List trademarks and trading names that the Spanish patent office records under a known company slug, returning JSON with status, dates, and counts for brand research.

Instructions

List the trademarks and trading names that the Spanish patent office (OEPM) records under a holder with this company's name.

Use it for a known company (a slug from search_companies or company_history); to go from a brand to its company use brand_owner.

Returns JSON {company_slug, commercial_names, trademarks (each {name, file, status, since}), counts, truncated, limit_per_kind, source, note}. The office publishes no tax IDs, so every link is a name match, not confirmed ownership. An empty result means none is linked in our data, not that the company holds none. limit applies to each kind separately, newest first; counts is what this answer lists, not the company's total, and truncated true for a kind means more are linked: raise limit.

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
limitNoMaximum results per kind (trademarks, trading names), integer 1-200, e.g. 10 (default 50).
companyYesCompany slug, as returned by search_companies or company_history, e.g. vaz-metales-sl.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.1.1
    • changedInput schema / properties / company / description
      Previous value: -"Company slug, as returned by search_companies or company_history."New value: +"Company slug, as returned by search_companies or company_history, e.g. vaz-metales-sl."
    • changedInput schema / properties / limit / description
      Previous value: -"Maximum results per kind (trademarks, trading names), 1-200 (default 50)."New value: +"Maximum results per kind (trademarks, trading names), integer 1-200, e.g. 10 (default 50)."
  2. Addedv1.1.1

TDQS

A4.9/5.0
Behavior5/5

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

Beyond the readOnly/idempotent annotations, it discloses the plan gate (basic or higher), the X-API-Key header, one request per call, and the critical caveat that links are name matches rather than confirmed ownership since OEPM publishes no tax IDs. It also explains empty-result semantics, per-kind limits, and what truncated means.

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?

Purpose is front-loaded, followed by usage, return shape, caveats, and access requirements. Every sentence carries information an agent would otherwise have to guess, with no filler or repetition of the 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?

There is no output schema, and the description fully enumerates the return shape including nested trademark fields. It also covers the truncation/limit interaction and the name-match reliability caveat, leaving no material gap for correct invocation or interpretation.

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 schema already documents both parameters. The description still adds real meaning for limit: it applies per kind, newest first, and truncated=true means raise it. The company parameter gains only the reiteration of the slug source, already in the schema.

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: lists trademarks and trading names recorded by OEPM under a holder matching the company name. It immediately distinguishes itself from the sibling brand_owner by naming the reverse direction, 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?

Explicitly says to use it for a known company and where the slug comes from (search_companies or company_history), and names the alternative brand_owner for the opposite lookup. Both the entry condition and the exclusion are stated.

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