Skip to main content
Glama

mocop

domain_dns_guide

Read-only

Where a claimed domain's DNS is hosted and the exact TXT record to publish (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": "domain_dns_guide"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety and locality are covered by structured data. The description adds one genuinely new behavioral fact — 'requires sign-in' — which is auth context the agent cannot get from annotations. It omits what happens for an unclaimed domain or domain not found, which would be the natural next disclosure.

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 short sentence with no wasted words, and the most useful content (DNS host plus TXT record) is front-loaded. It reads as a sentence fragment with no explicit verb, which is the only structural weakness.

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?

For a one-parameter read-only lookup with no output schema, the description usefully previews the return payload and the auth requirement, which is most of what an agent needs to invoke it. It stops short of explaining failure modes or the verification workflow it supports, leaving the tool adequate but not self-sufficient.

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% for the single parameter, so the description must carry the meaning. It constrains the input by calling it a 'claimed domain', implying the value must be a domain already added to the account rather than any arbitrary hostname — useful but thin for a 0%-coverage schema, with no format or example given.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The text is a noun phrase rather than a verb+resource statement, but it does specify the payload concretely: where a domain's DNS is hosted plus the exact TXT record to publish. It never states the action (lookup/retrieve) and does not differentiate itself from siblings like verify_domain or get_guide, so an agent must infer the operation.

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 explicit when-to-use guidance and no named alternative. The phrase 'a claimed domain' hints that this belongs to the domain-verification flow, but it never says to call this before verify_domain or instead of get_guide, leaving the agent to guess among roughly ten domain-related siblings.

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