Skip to main content
Glama

SafeSellAI

check_batch

批量商标词排查(每次最多 20 词,含 TRO 命中),返回完整明细。适用场景:手里有一批词或多条 Listing 标题要一次过筛。例:{"words":["词1","词2"]}。首次完成批量排查可解锁 +1 次免费店铺体检。匿名文字额度默认 100 词/天/IP;大批量排查请用 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": {
      "words": "<words>"
    },
    "name": "check_batch"
  }
}

Input Schema

NameRequiredDescriptionDefault
wordsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does well: it discloses the 20-word cap, that results include TRO hits, that full detail is returned, and the anonymous quota of 100 words/day/IP plus the API-Key workaround. It leaves the read-only nature and any failure modes implicit.

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?

The purpose is front-loaded, followed by use case, example, then limits and quota, so an agent can decide quickly. The “+1 次免费店铺体检” reward sentence is promotional rather than operationally useful and could be dropped without loss.

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?

For a one-parameter tool with no output schema, the description covers input shape, size limit, what is returned in principle, quota constraints, and the scaling alternative. Only the exact result fields and non-TRO hit semantics are left unstated.

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 0% for the single “words” parameter, so the description must compensate. It restates the 20-item cap already enforced by maxItems and adds a literal example payload ({"words":["词1","词2"]}), which clarifies the array-of-strings shape but adds nothing on format or content of individual terms.

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 opens with a specific verb plus resource (“批量商标词排查”), and immediately scopes it as batch (max 20 words) and inclusive of TRO hits, which implicitly separates it from the single-item alternatives check_brand and check_tro. It does not name a sibling explicitly, so sibling differentiation is only implied.

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 condition (“手里有一批词或多条 Listing 标题要一次过筛”) and routes large-volume work to the API Key path, which is a real alternative. It never states when not to use this tool, e.g., to prefer the single-word tools for one lookup.

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