Retrieve detailed WHOIS data for any .cl domain to check registration status, ownership, and expiration dates. Query NIC Chile directly for authoritative domain information.
Get detailed WHOIS information for a .cl domain
| Name | Required | Description | Default |
|---|---|---|---|
| domain | Yes | Domain name (e.g. google.cl) |
Changes observed during successful MCP inspections.
v1.0.3Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description indicates a read-only lookup operation but does not disclose potential behavior such as errors for unregistered domains, rate limits, or the detail level of the response. With no annotations, the description carries the burden but only partially fulfills it.
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?
A single, focused sentence with no extraneous words. It front-loads the action and target resource, making it appropriately sized and easy to parse.
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?
For a single-parameter, read-only tool, the description is nearly sufficient: it specifies the input and the type of output. However, since there is no output schema, the agent is left without details on what fields the WHOIS data will contain, so a minor gap remains.
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?
The input schema fully documents the 'domain' parameter with an example format, and the description adds no additional parameter semantics. Since schema description coverage is 100%, a baseline of 3 applies.
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?
The description uses the specific verb 'Get' and identifies the resource as 'detailed WHOIS information for a .cl domain'. This clearly distinguishes it from sibling tools like get_latest_domains, search_domains, and get_deleted_domains, which deal with domain lists and searches.
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?
No explicit when-to-use guidance is provided. Usage must be inferred from the tool name and sibling names; there is no sentence explaining that this is the tool to call for single-domain registration details rather than bulk lists.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.