Skip to main content
Glama

HokuHost Domains

renew_domain

Renew a domain; paid like create_order.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "domain": "<domain>"
    },
    "name": "renew_domain"
  }
}

Input Schema

NameRequiredDescriptionDefault
payNoauto (default): saved card if possible, else payment_url. link: always payment_url
waitNoSeconds to wait for payment/registration to finish (max 25)
yearsNo
domainYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

The annotations already state this is a non-read-only, non-idempotent, non-destructive operation, so the safety profile is mostly covered. The description adds only that payment behaves 'like create_order,' without explaining card charging versus payment URL behavior, retry implications, or failure/refund consequences.

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

Conciseness4/5

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

The description is a single front-loaded sentence with no filler. However, the cross-reference 'paid like create_order' is compressed to the point of ambiguity.

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?

For a paid, non-idempotent renewal with four parameters and no output schema, the definition omits renewal preconditions, default years, payment/URL outcomes, and failure behavior. The annotations cover safety but not the payment flow, leaving the definition incomplete for reliable invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema documents the pay and wait parameters, but the description adds little beyond restating that a domain is renewed and payment resembles create_order. It does not compensate for the undocumented years and domain semantics at 50% schema description coverage.

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

Purpose4/5

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

The verb 'Renew' and resource 'domain' are specific, and the note that payment works 'like create_order' gives some sibling context. It is clear this handles existing domain renewal rather than initial ordering, though the payment comparison is vague.

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?

Use is implied by 'Renew a domain,' and the create_order reference suggests payment flow context. However, there is no explicit when-to-use versus when-not-to-use guidance, such as whether the domain must already be registered or nearing expiry, nor an explicit alternative for new registrations.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources