Skip to main content
Glama

mocop

add_domain

Read-only

Claim a domain you own; returns the DNS TXT record or file to publish for verification (requires sign-in).

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": "add_domain"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior2/5

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

The description states the auth requirement and the return payload, which is useful. But "Claim a domain" implies a persistent state change to the caller's account while the annotations declare readOnlyHint=true (no environment modification), and the description never clarifies whether a pending claim is recorded or whether the call is purely informational — a tension an agent cannot resolve from the text.

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?

One front-loaded sentence: the action, the returned artifact, and the auth caveat in a compact parenthetical. No filler, though the claim/read-only ambiguity shows the brevity costs some precision.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description correctly describes what comes back (TXT record or file), which is the key missing piece. It does not cover behavior on an already-claimed domain, whether the record expires, or the handoff to a verification tool — gaps that matter for a claim/verify workflow.

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 0%, so the description carries the burden for the single parameter. "A domain you own" adds an ownership constraint and implies a bare domain name, but it gives no format example or guidance on subdomains, IDNs, or URL-vs-hostname input.

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?

"Claim a domain you own" plus the concrete return value ("the DNS TXT record or file to publish for verification") gives a specific verb, resource, and outcome. It implicitly positions itself as the first step before verification, though it never names verify_domain or domain_dns_guide explicitly.

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 parenthetical "(requires sign-in)" is a real prerequisite and the mention of a record to publish implies a follow-up verification step. However, there is no explicit statement of when to prefer this over domain_dns_guide or verify_domain, or what to do if the domain is already claimed, so usage is only implied.

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