Skip to main content
Glama

Wanmi.AI Domain Tools

SSL 证书检查

ssl-check

沿用站内公网 DNS、安全 TLS 握手与 CAA 检查,仅连接 443。过期、自签名等证书发现仍是成功诊断;上游失败、限流或不完整检查不计次。 使用现有 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": {
      "host": "<host>"
    },
    "name": "ssl-check"
  }
}

Input Schema

NameRequiredDescriptionDefault
hostYes

Output Schema

NameRequiredDescriptionDefault
dataYes
metaNo
stateYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/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 a lot of it: it discloses the auth requirement (an existing API key), that the call draws on API-center quota and may be billed, that upstream failure/rate limiting/incomplete checks are not counted, and that certain findings are still 'successful'. The main gap is that it doesn't state explicitly that the tool is read-only and never modifies the target.

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 compact sentences, front-loaded with the operational mechanics before the billing/counting caveats. Dense but every clause carries information; nothing is redundant padding.

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 single-parameter diagnostic with an output schema (so return values need no explanation) and no annotations, the definition covers cost, failure semantics, and the port constraint adequately. It falls short only on the input contract — the expected format of 'host' — which an agent must guess.

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?

The schema has one parameter, 'host', with 0% description coverage (only maxLength 253 is given). The description discusses DNS and port 443 but never says what a valid host looks like — bare hostname vs. URL with scheme, IP addresses, whether a port may be included — so it does not compensate for the schema gap.

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 the concrete mechanics — public DNS resolution, secure TLS handshake, and CAA check against port 443 — which makes clear this is a certificate/TLS diagnostic for a given host. It never states the purpose as a single verb+resource sentence and does not differentiate itself from siblings such as dns-lookup or website-check, which also probe a host.

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?

Usage is implied rather than stated: 'connect only to 443' tells the agent the tool is HTTPS-only, and the note that expired/self-signed findings still count as successful diagnostics tells it how to read the outcome. There is no explicit when-to-use / when-not-to-use guidance and no pointer to an alternative sibling for plain DNS or general website checks.

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