dns.send_renew_txRevalidate one to four owned .ton names and return one HTTPS page for a single TON Connect multi-message confirmation.
| Name | Required | Description | Default |
|---|---|---|---|
| domains | Yes |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Beyond annotations indicating a non-read-only, non-idempotent operation, the description adds that the tool returns an HTTPS page and involves a TON Connect multi-message confirmation, which clarifies the user interaction model. It does not detail prerequisites like ownership verification but mentions 'owned' names.
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?
The description is a single efficient sentence that front-loads the main verb and packs in all essential details without ambiguity.
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 tool with one parameter and no output schema, the description adequately covers the function and output. It could mention the next step after obtaining the link, but the 'confirmation' part implies the flow. Given the annotations cover safety, this is sufficiently complete.
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 0%, so the description must compensate. The description states 'one to four owned .ton names', which explains the domains parameter's purpose and bounds. However, it does not specify the string format (e.g., with or without .ton suffix).
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 clearly states the action ('Revalidate'), the resource ('owned .ton names'), and the output ('one HTTPS page for a single TON Connect multi-message confirmation'). This distinguishes it from sibling DNS tools like dns.lookup and dns.send_name_tx.
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?
The description implies usage for renewing .ton names but does not explicitly mention alternatives or when not to use it. No comparison with sibling transaction tools is provided, so the agent must infer from the tool name.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Tools are scoped by clear resource prefixes (auth, dns, sites, storage, subdomains) with specific actions. Some transaction tools share a similar 'send_*_tx' pattern and could be confused, but descriptions are detailed enough to distinguish them.
All tools follow a consistent '<domain>.<action>' pattern with snake_case, and transaction tools append '_tx'. The naming is uniform and predictable across all 46 tools.
At 46 tools, the server is heavily overloaded compared to typical MCP scopes. While the broad domain justifies some volume, the sheer number makes agent selection cumbersome and includes many highly specialized entries.
Core domains (sites, storage, subdomains, dns, auth) have robust lifecycle coverage including creation, reads, updates, deletes, and transaction confirmations. Minor gaps exist in payments (single tool) and media (no retrieval/deletion), but these are peripheral.