Skip to main content
Glama

domani

by run.domani

Renew Domain

renew_domain

Renew a domain you own for additional years. Always confirm with the user before calling this.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
yearsNoNumber of years to renew (1-10, default 1)
domainYesDomain to renew, e.g. mysite.com
max_priceNoCeiling in USD for the renewal charge. Fails with PRICE_ABOVE_MAX (nothing charged) if the real price is above it.
payment_txNoTransaction hash of a USDC payment already sent on-chain.
payment_chainNoChain the USDC payment was sent on.
payment_methodNoPayment method: 'card' to charge card on file, 'usdc' to pay with USDC. Overrides the user's default preference for this request.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changed
    • addedInput schema / properties / max_price
      Added value: +{
+  "description": "Ceiling in USD for the renewal charge. Fails with PRICE_ABOVE_MAX (nothing charged) if the real price is above it.",
+  "exclusiveMinimum": 0,
+  "type": "number"
+}
  2. First observed

TDQS

B3.4/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It fails to mention that this is a paid transaction involving charges to the user's payment method, that it has failure conditions (like PRICE_ABOVE_MAX), or that it will extend the domain's expiration date. The confirmation instruction is helpful, but critical financial implications are omitted.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two concise sentences with the purpose front-loaded and no wasted words. The second sentence adds an actionable reminder to confirm with the user, which is necessary for a financial mutation tool. It is appropriately sized for the complexity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite having six parameters, two enums, and no output schema, the description is minimal and omits essential context. It does not explain payment processing, success/failure return values, ownership verification, or how this tool relates to similar domain operations. For a tool that performs a paid action, this level of description is insufficient.

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?

The input schema already provides 100% description coverage for all parameters, including details like default years, payment method enums, and max_price behavior. The description adds little beyond the phrase 'additional years' which somewhat corresponds to the years parameter. Since the schema does the heavy lifting, a baseline score of 3 is appropriate.

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

Purpose5/5

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

The description clearly states a specific action: 'Renew a domain you own for additional years.' It uses a specific verb ('renew') and resource ('domain you own'), which distinguishes it from sibling tools like acquire_domain or buy_domain. The ownership qualifier prevents confusion with domain acquisition.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies the usage context (renewing an already-owned domain) and includes an important behavioral instruction ('Always confirm with the user before calling this'). However, it does not explicitly state when to use this tool versus alternatives, such as set_auto_renew or transfer_domain, nor does it provide exclusionary guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All domani toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.5/5.0
Disambiguation3/5

While most tools have distinct purposes, several clusters overlap significantly (e.g., check_email, check_email_deliverability, get_email_deliverability, get_domain_email_status; buy_domain, buy_aftermarket, acquire_domain). The descriptions are detailed and help differentiate, but the sheer number of tools makes it challenging for an agent to select the correct one without careful reading.

Naming Consistency3/5

The dominant pattern is verb_noun with underscores (e.g., create_mailbox, list_domains), but there are notable inconsistencies: destructive actions mix delete/remove/cancel/revoke/unsell, and a few names deviate entirely (search, dns_check, domain_status). The pattern is recognizable but not uniformly applied.

Tool Count1/5

With 122 tools, this vastly exceeds the 50+ threshold for extreme mismatch. Even for a comprehensive domain and email platform, the tool count is overwhelming and will likely hinder agent performance through excessive choice and context bloat.

Completeness4/5

The server covers a wide range of domains, DNS, email, marketplace, negotiations, transfers, webhooks, tokens, and billing. Minor gaps exist, such as no update operation for mail rules, no direct domain deletion, and limited mailbox configuration beyond forwarding and credentials, but most lifecycle workflows are supported.

Resources