Skip to main content
Glama

A company's brands

company_brands
Read-onlyIdempotent

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

Use it with 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}: one entry per OEPM file, so a name can repeat, the company's own name included. No tax IDs are published: each link is a name match, not confirmed ownership. An empty list means none is linked in our data, not that the company holds none; {error, suggested_companies} means an unknown slug: nothing was looked up. limit applies per kind, 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).

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

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. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive, non-open-world behavior, and the description still adds substantially: name-match rather than confirmed ownership, no tax IDs, empty-list vs not-linked distinction, per-kind limit with newest-first ordering, truncated semantics, error payload, and a plan/API-key requirement. This is well beyond the annotations, though the API-key and plan detail sits at the end where it is easy to miss before invoking.

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 is front-loaded and each paragraph carries distinct content (return shape, caveats, auth). It is dense and runs long in a single block, so the auth/plan requirement buried at the end is easy to skim past, costing a point on structure.

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 and a mutation-free read tool, the description fully specifies the return object shape, the repeat-per-file caveat, the error shape, and the plan/auth prerequisite. Almost nothing an agent needs in order to call this correctly is missing.

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 a 3, but the description adds real meaning the schema lacks: limit is applied per kind, results are newest first, and truncated=true means the caller should raise limit. The company parameter's link semantics (name match, not ownership) also enrich what a 'slug' means here.

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?

Names a specific verb (list) and resource (trademarks and trading names recorded by OEPM under a holder matching the company name), and implicitly draws the boundary against brand_owner by describing the reverse direction. No ambiguity with sibling tools remains after reading the first sentence.

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 states its input comes from search_companies or company_history, and points to brand_owner for the reverse lookup. It also flags the failure mode (unknown slug) so the agent knows what to do when the precondition is not met.

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.