Skip to main content
Glama

SafeSellAI

check_tro

查询单个品牌词的 TRO 涉诉命中摘要。适用场景:只想先确认某个词有没有 TRO 案件。例:{"brand":"nike"}。完整 TRO 案件检索请用 API Key。匿名额度与 check_brand 共用。

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_tro"
  }
}

Input Schema

NameRequiredDescriptionDefault
brandYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

No annotations are supplied, so the description alone must carry the behavioral burden. It helpfully discloses that the anonymous quota is shared with check_brand and that full case retrieval needs an API Key, which are real limits an agent should know, but it does not say what the '摘要' contains or how hits are reported when no case exists.

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?

Four short sentences, front-loaded with the purpose and followed by use case, example, then limits. Every sentence adds distinct information with no repetition.

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 lookup with no output schema, the description covers purpose, example input, quota sharing, and where to go for full retrieval. The remaining gap is the shape of the returned summary and no-hit behavior, but for a lightweight pre-check tool this is close to complete.

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 description coverage is 0% for the single 'brand' string, so the description must add meaning. It identifies the value as a single brand keyword and supplies a concrete call example ({"brand":"nike"}), clarifying format and singularity that the bare schema does not.

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: it returns a TRO litigation hit summary for a single brand keyword, and explicitly scopes it to 'just checking whether a word has TRO cases'. This contrasts with the full TRO case search, which requires an API Key, so an agent can distinguish it from the broader retrieval path.

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 an explicit use case ('只想先确认某个词有没有 TRO 案件') and names the alternative for complete case retrieval (API Key required). It does not name a sibling repeatedly for the same behavior, but the auth requirement for the fuller search is signaled only indirectly, with no statement of whether this tool itself needs a key.

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