Skip to main content
Glama

SouthPow crypto & market data

buy_domain_whois

Paid. Domain WHOIS / RDAP lookup: registrar, created and expiry dates, age, status, nameservers, DNSSEC. $0.02 USDC on Base or Solana. No account, no API key. Failed calls not charged. URL https://southpow.media/v1/domain/whois.

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": {
      "domain": "<domain>"
    },
    "name": "buy_domain_whois"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYesDomain, e.g. example.com

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations at all, the description carries the full burden and does substantial work: it discloses the paid model, the exact price and accepted payment chains, no auth/account requirement, and a favorable failure policy ('Failed calls not charged'). Missing only latency, rate limits, and error-shape behavior.

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 the resource and returned fields, then pricing and payment terms, with zero filler sentences. The trailing endpoint URL is of marginal use to a calling agent but does not bloat the definition.

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 one-parameter lookup with no output schema, this is close to complete: it says what data is returned, what it costs, how to pay, and that failures are free. Only failure modes and result-shape guidance are absent, which is a minor gap at this complexity.

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 coverage is 100% and the single 'domain' parameter is already documented with an example in the schema, so the description owes little. It adds no format rules of its own (e.g., whether subdomains, IDNs, or bare TLDs are accepted), so baseline 3 applies.

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 ('Domain WHOIS / RDAP lookup') and enumerates exactly what comes back: registrar, created/expiry dates, age, status, nameservers, DNSSEC. This is enough to distinguish it from the sibling buy_domain_dns, which is the only adjacent tool in the list.

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 description gives context (paid lookup, pricing, no account needed) but never states when to pick this over buy_domain_dns or when not to call it. The WHOIS-vs-DNS distinction is implied by the returned fields rather than spelled out, so routing is left to inference.

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