Skip to main content
Glama

SafeSellAI

store_audit

免费店铺体检:提交商品清单 items(标题/品牌/卖点/描述),逐个做文字维度排查(商标词 + TRO),返回完整明细与风险汇总。单次最多 100 个 SKU(env MCP_GUEST_AUDIT_MAX_SKU 可配);免费次数 = 基础 1 次 + 首次 check_batch 奖励 1 次(剩余查 guest_info)。图片版权/外观专利/平台合规维度不在免费版内。绑定店铺模式(storeId)需要账号在网页版绑定自有店铺并用店铺凭证拉商品,匿名没有账号与凭证、不可用,请使用 API Key。例:{"items":[{"title":"Water Bottle 32oz","brand":"Acme"}]}

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

Input Schema

NameRequiredDescriptionDefault
itemsNo
storeIdNo
maxItemsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/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 well: it discloses quota economics, the SKU cap and its env override, the specific dimensions excluded from the free version, and the authentication prerequisite for storeId mode. It stops short of stating whether the call mutates anything or how long a batch run takes, which limits it to a 4.

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?

Information-dense but front-loaded: purpose first, then limits, quota, exclusions, auth caveat, and a concrete example. The semicolon-chained clauses and parenthetical env/quota details are slightly heavy, but each carries operational value rather than filler.

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 3-parameter tool with no annotations, no output schema, and zero schema coverage, the description fills most of the gap: scope, limits, quota, auth, and exclusions are all covered. Remaining holes are the undocumented item fields (sku, images, category) and the maxItems parameter's exact meaning.

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%, so the description must compensate, and it does so only partially. It explains items content (title/brand/features/description) and gives a worked example, and it explains storeId mode thoroughly, but it never mentions sku, images, category, or what the maxItems parameter does relative to the stated 100-SKU cap.

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+resource: a free store audit that takes a product list (items) and runs per-item text-dimension checks for trademark words and TRO, returning detail plus a risk summary. It also implicitly scopes itself against siblings by excluding image copyright / design patent / platform-compliance dimensions, which are covered by check_image-style tools.

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

Usage Guidelines5/5

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

Explicit about when it applies and when it does not: free-tier text-only batch audit, capped at 100 SKUs, quota = 1 base + 1 bonus for first check_batch (remaining quota via guest_info), and storeId mode unavailable to anonymous users who must use an API key. That is a near-complete when/when-not map.

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