Skip to main content
Glama

SouthPow crypto & market data

buy_domain_dns

Paid. DNS lookup for a domain: A, AAAA, MX, NS, TXT, CNAME and CAA records. $0.01 USDC on Base or Solana. No account, no API key. Failed calls not charged. URL https://southpow.media/v1/domain/dns.

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_dns"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYesDomain, e.g. example.com

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does substantial work: it discloses that the call is paid ($0.01 USDC on Base or Solana), that no account or API key is required, and that failed calls are not charged. It omits rate limits, timeouts, and whether all record types are always returned or must be requested.

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 'Paid.' and then the capability, so cost and function land immediately. The fragment style is telegraphic but nothing is wasted; the endpoint URL is the only element that could be considered incidental.

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 read tool with no output schema, the description covers what is returned (the enumerated record types) and the commercial terms, which an agent needs before spending money. Missing only the response shape and failure conditions, which are minor here.

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% for the single `domain` parameter, which already carries an example. The description adds the context that the domain is the subject of a DNS record lookup, but no format rules, TLD restrictions, or normalization behavior beyond the schema. Baseline 3 is appropriate.

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 concrete verb+resource ('DNS lookup for a domain') and enumerates the record types returned (A, AAAA, MX, NS, TXT, CNAME, CAA), so an agent knows exactly what it gets. It does not explicitly distinguish itself from the sibling buy_domain_whois or buy_ssl_check, which keeps it short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

There is no guidance on when to choose this over buy_domain_whois or buy_ssl_check, and no stated prerequisites or exclusions. The use case is inferable from the record list, but routing between the three domain-related siblings is left entirely to the agent.

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