Skip to main content
Glama

HokuHost Domains

get_prices

Read-only

USD per year for every extension; next = announced price change; restore_usd = fee to restore an expired domain.

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": "get_prices"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered by structured data. The description adds useful output semantics ('next' is an announced change, 'restore_usd' is an expiry-restore fee), but says nothing about freshness of prices, whether all TLDs are included, or the shape of the returned structure.

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?

A single semicolon-delimited sentence with zero filler, front-loading the core information (USD per year, every extension) and then defining the two non-obvious keys. Nothing is redundant.

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?

With no input parameters and no output schema, the description's field glossary does real work in compensating for the missing return schema. However, it never states the overall response shape (e.g., a map keyed by extension) or whether the listing is exhaustive, which leaves an agent guessing at how to read the result.

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 tool takes zero parameters, so there is no parameter semantics to explain and the baseline of 4 applies. The description instead spends its words on return-value keys, which is the more relevant gap here.

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 identifies the resource (prices per extension) and its unit (USD per year), which is enough to separate it from siblings like get_domain, renew_domain, or search_domains. It lacks an explicit verb such as 'returns' or 'lists', so the action is inferred rather than stated, but the resource 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 Guidelines2/5

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

There is no when-to-use guidance and no reference to alternatives, even though siblings such as renew_domain and create_order clearly involve pricing decisions. The agent gets no hint about whether this is a pre-purchase lookup, a general price table, or something to call before renew_domain.

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