Skip to main content
Glama
Sign In
commune-mcp

commune-mcp

Official
by commune-dev
OverviewSchemaSourceRelated ServersDiscussions(1)Admin
Python
Remote

get_domain_records

Retrieve MX, TXT, and CNAME records needed to verify a domain before calling verify_domain.

Instructions

Get the DNS records required to verify a domain.

Returns MX, TXT, and CNAME records that must be added at your domain registrar before calling verify_domain.

Args: domain_id: The domain ID (from list_domains)

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_id": "<domain_id>"
    },
    "name": "get_domain_records"
  }
}

Input Schema

NameRequiredDescriptionDefault
domain_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.2/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full transparency burden. It correctly specifies the return types (MX, TXT, CNAME) and the registrar context, but it does not explicitly state that the operation is read-only/no side effects, nor does it mention potential error conditions, leaving some gaps.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely concise and front-loaded, with the main purpose stated first. The return type summary and the parameter explanation each add value with no wasted words.

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 tool with a single parameter and an output schema, the description covers the essential purpose, usage context, and parameter origin. The output schema handles return structure, so the description is sufficiently complete, though it could mention error scenarios.

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?

The input schema only defines 'domain_id' as a string with 0% description coverage. The description compensates by explaining that the ID comes from list_domains, adding practical source context that the schema lacks.

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?

The description clearly states the verb 'Get' and the resource 'DNS records required to verify a domain.' It explicitly distinguishes from the sibling verify_domain by explaining these records are prerequisites for that action.

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?

The description provides clear context by stating 'before calling verify_domain,' indicating when this tool should be used. It does not explicitly name alternatives or when-not scenarios, but the guidance is clear enough for a simple read operation.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools