Skip to main content
Glama

Wanmi.AI Domain Tools

网站检测

website-check

同步返回站内网站检测报告。mode=check 为完整检测,http 仅检查 HTTP。复用 guarded-http 的公网/端口/重定向防护、目标限流和请求预算;不需要游客验证码。警告是有效诊断;检查项执行失败时不计次。响应超过 64 KiB 返回错误且不计次。 使用现有 API key 调用,沿用 API 中心额度与计费,可能收费。

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": "website-check"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYes
modeNo

Output Schema

NameRequiredDescriptionDefault
checksYes
finalUrlNo
checkedAtYes
requestedUrlYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/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 so well: it discloses synchronous return, reuse of guarded-http SSRF-style protections (public network, port, redirect), per-target rate limiting, request budget, that warnings are valid diagnostics, that failed check items and oversized (>64 KiB) responses do not count against quota, and that calls use the API key with possible billing.

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?

Front-loaded with purpose, then mode semantics, then protection/failure behavior, then billing. Every sentence adds information, though the run of clauses about protections, quotas, and size limits is dense and could be split for easier scanning.

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

Completeness5/5

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

For a two-parameter tool with an output schema (so return shape need not be described) and no annotations, the description covers cost, safety protections, rate limits, failure accounting, and size limits. An agent has what it needs to call it correctly and predict charges.

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%, so the description must compensate. It fully explains the mode enum (check = full check, http = HTTP only), though the url parameter is left to its self-evident name and the 2048-length constraint is only in the schema.

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?

States a specific verb and resource: synchronously returns a website check report, and immediately splits it into two modes (full check vs HTTP-only). It is clear what the tool does, though it does not explicitly distinguish itself from siblings like ssl-check or whois, so an agent must infer the boundary.

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?

The mode values give implicit selection guidance (complete check vs HTTP-only check), which is helpful for choosing between the two behaviors. However, there is no stated when-to-use versus the sibling verification tools, and no prerequisites or exclusions beyond noting no guest captcha is required.

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