Skip to main content
Glama

SafeSellAI

check_image

单图检查(文字、图形商标、TRO)。适用场景:单张商品图查商标与 TRO 风险。匿名试用暂未开放查图。

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "check_image"
  }
}

Input Schema

NameRequiredDescriptionDefault
image_b64No
image_urlNo
own_brandsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/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. It usefully discloses that anonymous trials cannot currently perform image checks, which is a real access constraint, but says nothing about how image_b64 and image_url interact, rate limits, or what a result contains.

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 name and purpose are front-loaded in the first clause, followed by scenario and the trial caveat, with no filler. It is efficient, though bordering on under-specified rather than truly concise.

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

Completeness2/5

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

For a 3-parameter tool with no annotations, no output schema, and zero schema coverage, the description is too thin. An agent still cannot tell whether to supply a URL or base64 data, whether one is required, or what own_brands does.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There are 3 parameters at 0% schema description coverage, so the description must compensate. It does not: neither the two alternative image-input fields (base64 vs URL) nor own_brands is explained anywhere.

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 names a specific verb and resource: single-image checking covering text trademarks, graphic trademarks, and TRO. '单图' implies a single-image scope, which contrasts impliedly with check_batch, but the sibling is never named, so differentiation is left to inference.

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

Usage Guidelines3/5

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

'适用场景:单张商品图查商标与 TRO 风险' gives a clear usage context, but there is no explicit when-not guidance and no alternative tool is named for batch or brand-only workflows. Usage is conveyed but not routed.

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