ClawDaddy MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
No tools | |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 14 tools
Each tool has a clearly distinct purpose targeting specific DNS/domain management operations, with no ambiguity or overlap. For example, add_dns_record, delete_dns_record, and update_dns_record are clearly separated, and tools like get_quote and purchase_domain handle distinct purchase-related tasks.
Tool names follow a highly consistent verb_noun pattern throughout, such as add_dns_record, delete_dns_record, get_domain_info, and update_settings. All tools use snake_case and clear action verbs, making the naming predictable and readable.
With 14 tools, the server is well-scoped for domain registration and DNS management, covering key operations like lookup, purchase, DNS CRUD, settings, and token recovery. Each tool earns its place without being excessive or insufficient for the domain.
The tool set provides complete coverage for the domain registration and management lifecycle, including availability checks, purchasing, DNS record CRUD, settings management, nameserver handling, and token recovery. There are no obvious gaps, enabling agents to perform all essential workflows without dead ends.