Skip to main content
Glama

HokuHost Domains

list_domains

Read-only

Domains in the account with expiry dates.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, so the safe-read profile needs no restating. The description contributes one piece of behavioral value beyond that: results include expiry dates. It says nothing about pagination, result size, or whether expired domains are included, which are the traits an agent would actually need.

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

Conciseness3/5

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

It is only six words and front-loads the resource, so nothing is wasted. However, it is a noun phrase rather than a statement, and the terseness crosses into under-specification given the ambiguity with search_domains.

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?

This is a trivial no-parameter read with no output schema, so the bar is low, and naming the expiry-date field helps. Still, an agent cannot tell from this alone whether the call returns all domains or a subset, or how to choose it over the sibling search tool.

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 and the schema is an empty object, so there is no parameter meaning to add. Baseline 4 applies; the description correctly implies an unfiltered account-wide listing.

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

Purpose3/5

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

The fragment "Domains in the account with expiry dates" identifies the resource (domains) and its scope (the account) plus one returned field, but omits an explicit verb such as 'list'. It also does not distinguish this from the sibling search_domains, so an agent must infer which of the two to call.

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 exclusion or alternative named. The presence of a sibling named search_domains makes the absence of any routing hint a real gap, since nothing states whether this is the unfiltered enumeration or a filtered lookup.

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