Skip to main content
Glama

trademark_owner_search

按目标国家查询 One1 已覆盖的商标数据,检索权利人/申请人名下记录。

用于做竞品权利人画像、查某公司商标布局、识别高频维权方。
owner: 权利人/公司名,如 "Nike, Inc."。
live_only: 仅 Live,默认 False。limit: 默认 20。
返回: {owner, count, results:[{mark, nice_class, legal_status, risk_level, tro_alert?}]}。

country: 单个国家/地区代码,不是任意 ISO 代码;去首尾空白并转大写。省略、空串或纯空白默认 US。英国使用 UK,欧盟 EU,马德里国际注册 WO;不接受多国列表。文本本地配置支持:AR, AT, AU, AZ, BR, CA, CL, CN, CZ, DZ, EE, ES, EU, FI, FR, GE, HR, ID, IE, IL, IN, IT, JP, KH, KR, LT, MX, NO, NZ, PL, PT, PY, RO, SG, SK, TW, UA, UK, US, VN, WO。实际文本检索合作方路由为 BX/DE/ES/IT/TR;BX 未列入覆盖快照,覆盖未验证。编号/权利人工具仅查本地源,能力与文本检索不同。历史图形接口还接受 USPAT 等设计库代码,返回专利图形候选,不代表商标国家覆盖。图形以 coverage_info 的 graphic_served 和实际后端可用性为准,可能有 ARIPO/OAPI 等地区代码。 先调用 coverage_info(country="") 获取覆盖清单,再以目标代码查询各国覆盖。全表来自静态快照,单国优先后端、失败回落静态;注意 warning、scope 和 clearance_ok(工具输出不含数据截止日字段,需要截止日请让用户查 https://one1.cn/api/coverage?country=XX)。各国数据范围、截止时间和完整性不同,多国支持不等于全球全量覆盖;无命中不等于可注册或不侵权。coverage.clearance_ok=false 时不能给可注册结论;true 也不是法律保证。count 是返回数量(文本近似检索为邻居数量),不是冲突数;结合 has_conflicts、conflict_count 和逐条风险信号判断。visual_similarity 不是侵权概率。TRO/enforcement 是库内信号,需核对来源和时间。USPTO/TSDR 仅适用于美国记录,其他国家核对相应官方来源。US 请求仅为示例。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
ownerYes
countryNo单个国家/地区代码,不是任意 ISO 代码;去首尾空白并转大写。省略、空串或纯空白默认 US。英国使用 UK,欧盟 EU,马德里国际注册 WO;不接受多国列表。文本本地配置支持:AR, AT, AU, AZ, BR, CA, CL, CN, CZ, DZ, EE, ES, EU, FI, FR, GE, HR, ID, IE, IL, IN, IT, JP, KH, KR, LT, MX, NO, NZ, PL, PT, PY, RO, SG, SK, TW, UA, UK, US, VN, WO。实际文本检索合作方路由为 BX/DE/ES/IT/TR;BX 未列入覆盖快照,覆盖未验证。编号/权利人工具仅查本地源,能力与文本检索不同。历史图形接口还接受 USPAT 等设计库代码,返回专利图形候选,不代表商标国家覆盖。图形以 coverage_info 的 graphic_served 和实际后端可用性为准,可能有 ARIPO/OAPI 等地区代码。US
live_onlyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / country / description
      Added value: +"单个国家/地区代码,不是任意 ISO 代码;去首尾空白并转大写。省略、空串或纯空白默认 US。英国使用 UK,欧盟 EU,马德里国际注册 WO;不接受多国列表。文本本地配置支持:AR, AT, AU, AZ, BR, CA, CN, CZ, DZ, ES, EU, FI, FR, GE, HR, ID, IE, IL, IN, IT, JP, KR, MX, NO, NZ, PL, PT, PY, RO, SG, SK, TW, UA, UK, US, VN, WO。实际文本检索合作方路由为 BX/DE/ES/IT/TR;BX 未列入覆盖快照,覆盖未验证。编号/权利人工具仅查本地源,能力与文本检索不同。历史图形接口还接受 USPAT 等设计库代码,返回专利图形候选,不代表商标国家覆盖。图形以 coverage_info 的 graphic_served 和实际后端可用性为准,可能有 ARIPO/OAPI 等地区代码。"
  2. First observed

TDQS

A4.1/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does so extensively: it explains static-snapshot vs per-country backend with fallback, the meaning of warning/scope/clearance_ok, that count is a result count (neighbor count for approximate text) rather than a conflict count, that visual_similarity is not an infringement probability, and that TRO/enforcement are in-library signals needing source verification. It also warns that no hits do not imply registrability or non-infringement.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose and return shape are front-loaded, which is good, but the country block is enormous and repeats essentially verbatim what the schema already documents, and the caveat section is a dense run-on. Several sentences re-explain coverage limitations multiple times, so signal-to-noise suffers.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, but the description supplies the return shape ({owner, count, results:[{mark, nice_class, legal_status, risk_level, tro_alert?}]}) and the major data-freshness and interpretation caveats. Combined with the coverage_info-first workflow, an agent has enough to call and interpret results, though field-level semantics for the returned objects remain thin.

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 only 25% (country alone), so the description must compensate, and it does: owner is defined with an example ("Nike, Inc."), live_only is explained as live-only filtering with default False, and limit's default 20 is stated. The country text largely duplicates the schema description rather than adding new meaning, so it is not a full 5.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource: query trademark data for a target country and retrieve records under an owner/applicant name. It also differentiates somewhat from siblings by noting that number/owner tools only query the local source while text search differs. That differentiation is present but buried mid-paragraph rather than front-loaded.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

Gives concrete use cases (competitor owner profiling, mapping a company's trademark portfolio, spotting frequent enforcers) and prescribes a workflow: call coverage_info first, then query per-country. No explicit when-not or comparison against siblings like trademark_owner_profile is stated, so it stops short of full routing guidance.

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.