Register up to 100 domains in a single operation using default registration settings. Optionally specify currency and coupon code for payment.
Register multiple domains at once (up to 100). All domains are registered with default settings unless overridden.
| Name | Required | Description | Default |
|---|---|---|---|
| coupon | No | Coupon code for discount | |
| domains | Yes | List of domain names to register | |
| currency | No | Currency for payment |
Changes observed during successful MCP inspections.
v1.3.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so description must fully disclose behavior. It mentions 'default settings unless overridden' but no override parameters exist in schema, creating confusion. Lacks info on auth needs, rate limits, partial failures, or cost implications.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two concise sentences, front-loaded with key information (batch operation, limit, defaults). No redundant words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Without output schema or annotations, description lacks details on return value, error handling (e.g., partial failures in batch), and post-registration steps. For a 3-param batch tool, more completeness is needed.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, providing baseline. Description adds minimal context: 'default settings' for domains, but nothing for currency or coupon. No format or constraints beyond schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Description uses specific verb 'register multiple domains' and resource 'domains', with a clear batch scope (up to 100). Differentiates from sibling 'register_domain' which handles single domains.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicitly states 'Register multiple domains at once', implying use for batch operations. Does not explicitly exclude single-registration use case or reference 'register_domain' directly, but the context makes the distinction clear.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.