Skip to main content
Glama

HokuHost Domains

account

Idempotent

Get the account (owner details, saved card, limits). Pass fields to set the domain owner (registrant) details; needed before the first order.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "account"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityNo
kindNo
phoneNowith country code, e.g. +1 408 555 0100
stateNo
postalNo
streetNo
companyNo
countryNo2-letter code, e.g. US
full_nameNo
company_noNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true and destructiveHint=false, so safety is partly covered; the description adds that the returned payload includes owner details, saved card and limits, and that the write mode has a prerequisite (before the first order). It does not disclose whether a partial field set overwrites or merges existing registrant data, nor the consequences of an incomplete address.

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?

Two short sentences, front-loaded with the read behavior and followed by the write condition; no filler. The phrasing 'Pass fields' is slightly vague about which fields, but overall it is tight.

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

Completeness3/5

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

For a ten-parameter, two-mode tool with no output schema and thin schema documentation, the description conveys the essential duality and one prerequisite, but leaves open partial-update semantics, field groupings, and whether read results are filtered by permissions. Adequate but with clear gaps.

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?

Schema description coverage is only 20% (only phone format and country code are documented, plus the kind enum). The description groups all ten fields as 'domain owner (registrant) details' but never explains company_no, state, postal, or whether fields must be supplied as a coherent set. With such low coverage, the description is expected to compensate and largely does not.

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 description states a specific verb+resource ('Get the account') and enumerates the contents (owner details, saved card, limits), then adds a second mode ('Pass fields to set the domain owner (registrant) details'). This makes the tool's dual read/write nature clear and separates it from siblings like get_order or list_domains. It stops short of explicitly naming an alternative, but the purpose is unambiguous.

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 conditional 'Pass fields to set... needed before the first order' gives a real when-to-use cue for the write mode, and implicitly the omission of fields means read. However, there is no explicit statement of when to call it for reading versus when to call setup_card or get_domain, and no warning about when not to overwrite registrant data.

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