Skip to main content
Glama

Wanmi.AI Domain Tools

域名展示价格

domain-pricing

1~10 个后缀的标准域名展示价,显式使用 display_snapshot。金额为整数人民币分,不构成交易报价;不提供溢价域名价格。stale 保留历史价格与时间,purchaseEligible 始终 false。 使用现有 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": {
      "tlds": "<tlds>"
    },
    "name": "domain-pricing"
  }
}

Input Schema

NameRequiredDescriptionDefault
tldsYes1~10 个后缀;仅标准域名展示价,不查询溢价域名价格

Output Schema

NameRequiredDescriptionDefault
dataYes
metaNo
stateYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/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 substantial work: integer RMB cents, non-binding pricing, premium domains excluded, stale entries retain historical price and timestamp, purchaseEligible is always false, and calls consume existing API-key quota and may be billed. The only real gap is that call concurrency or rate-limit behavior for the billing impact is unstated.

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?

Four compact segments front-load the scope, then pricing semantics, then the billing caveat, with no filler. The telegraphic semicolon style is dense but every clause carries information.

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 single-parameter read-only pricing lookup with an output schema, the description covers scope, exclusions, unit, output-field caveats (stale, purchaseEligible), and cost implications. An agent has everything needed to decide and call correctly.

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 100% and the single tlds parameter already documents the 1–10 suffix limit and the standard-only restriction. The description restates the same constraint rather than adding format or syntax detail, so baseline 3 applies.

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 verb+resource: returning standard domain display prices for 1–10 TLDs, and notes the display_snapshot basis. It implicitly separates itself from siblings like domain-availability by being price-only, but never names an alternative, 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 Guidelines4/5

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

It gives a clear when-not boundary (no premium domain prices) and warns the figures are not trading quotes, which steers an agent away from treating them as offers. What is missing is any explicit pointer to which sibling tool to use when premium prices or availability are actually wanted.

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