Skip to main content
Glama

SafeSellAI

check_brand

使用公开商标词排查检查单个品牌/关键词(含 TRO 命中),返回完整明细。适用场景:拿不准一个词能不能用在标题/品牌里时先查它。例:{"brand":"nike"}。匿名文字额度默认 100 词/天/IP(env MCP_GUEST_TEXT_WORDS_DAILY 可配);更多额度与全部功能请用 API Key 连接。

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": "check_brand"
  }
}

Input Schema

NameRequiredDescriptionDefault
brandYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose real operational context: anonymous quota of 100 words/day/IP, an env override, and that an API key unlocks more quota and all features. It does not explicitly state that the call is read-only/non-mutating or what a 'TRO hit' result implies, so the safety profile is only inferable from the verb.

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?

Four compact sentences, front-loaded with the core action and followed by the use case, an example, and quota terms; nothing is redundant. The quota sentence is dense but earns its place by setting expectations before the agent hits a limit.

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

Completeness3/5

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

For a tool with no output schema, 'returns full details' is too vague — the agent cannot anticipate whether it gets a boolean, a risk score, or matched term lists. Usage, quota, and input example are covered well, so only the return-value gap keeps this at a 3.

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 0% for the single required 'brand' string, so the description must compensate. The example {"brand":"nike"} and the phrase '品牌/关键词' do clarify that free-form keywords are accepted, not just brand names, which adds meaning beyond minLength:1 — but format constraints (length, casing, multi-word phrases) remain unstated.

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?

The description states a specific verb and resource: screening a single brand/keyword against public trademark terms, including TRO hits, with full detail returned. The word '单个' (single) implicitly separates it from the batch sibling, though it never names that sibling or resolves overlap with check_tro, which is odd given this tool already covers TRO hits.

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?

It gives a concrete when-to-use trigger: check first when unsure whether a word can be used in a title or brand. What is missing is the when-not side — nothing tells the agent to prefer check_batch for multiple terms or check_tro for TRO-only queries, despite those siblings existing.

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.

Resources