Skip to main content
Glama

HokuHost Domains

create_order

Register 1–10 available domains for the owner. Pays with the saved card (then waits for the registry) or returns payment_url for the owner.

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": {
      "domains": "<domains>"
    },
    "name": "create_order"
  }
}

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
domainsYese.g. ["pixelstudio.com"]

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare write, open-world, non-idempotent, and non-destructive behavior, while the description adds important side effects: saved-card payment, possible payment_url fallback, and waiting for registry. It still omits pricing confirmation, failure/duplicate handling, and whether a pending order is created, so it is strong but not exhaustive.

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?

Two tightly written sentences with the core action and payment outcome front-loaded. There is no redundant or decorative wording.

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

Completeness4/5

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

For a four-parameter write tool with rich annotations and no output schema, it covers the essential registration, payment, and wait outcomes. It leaves some gaps around the exact return shape beyond payment_url, pricing confirmation, and how years affects registration.

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

Parameters4/5

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

The schema documents pay and wait clearly and gives a domains example, but years has no schema description. The definition adds a meaningful otherwise-missing 1–10 domain limit and the 'available' precondition, and explains the auto/link payment paths, though it does not clarify years.

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?

States a specific verb and resource: registering 1–10 available domains for the owner. The scope and 'available' qualifier distinguish it from list/get/search and renewal siblings, though it does not explicitly name alternatives like search_domains or renew_domain.

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 phrase 'available domains' implies domains should be confirmed before use, but the definition gives no explicit when-to-use guidance or rule for choosing this over renew_domain or search_domains. The payment-path explanation is behavioral rather than alternative-selection guidance.

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