Skip to main content
Glama

SafeSellAI

check_link

Listing 多维评分(商品 URL / ASIN / Walmart Item ID)。适用场景:给一条现成商品链接做全面体检。匿名试用暂未开放。

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": {
      "url": "<url>"
    },
    "name": "check_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full disclosure burden. It implies a read-only scoring operation and hints that authentication is required ('匿名试用暂未开放'), but says nothing about cost/credits, rate limits, marketplace coverage, or what '多维评分' actually returns. The auth hint is the only concrete behavioral disclosure.

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?

Two short sentences with the purpose front-loaded and no filler beyond the tangential trial-availability note. The mixed-language and compressed phrasing make it slightly harder to scan than an equivalent single-language statement, but nothing is wasted.

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 one-parameter tool with no annotations and no output schema, the description covers purpose and accepted input forms but leaves the agent guessing about the response shape and the meaning of the scoring dimensions it advertises. Adequate, but not complete for a tool whose whole value proposition is the output.

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 coverage is 0% and the only param is a bare 'url' string. The description compensates meaningfully by stating that a product URL, an ASIN, or a Walmart Item ID are all accepted forms, which an agent could not infer from the schema. It still gives no format examples or validation rules.

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 action and object: 'Listing 多维评分' for a product URL / ASIN / Walmart Item ID, plus the frame '全面体检' (full health check) on an existing product link. That is enough to distinguish it from a pure URL validator. It falls short of 5 because it never contrasts itself with siblings such as check_batch or store_audit.

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?

'适用场景:给一条现成商品链接做全面体检' implies the single-link case ('一条'), which suggests when to use it. There is no explicit statement of when NOT to use it, no mention of a batch alternative, and no prerequisites beyond the vague '匿名试用暂未开放' line.

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