list_domains
List a site's custom domains with live status (delegated, TLS ready, live). Requires a key.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| key | Yes | ||
| name | Yes |
boomurl
by com.boomurl
TDQS
C2.7/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must fully disclose behavioral traits. It mentions 'live status' but fails to specify whether the tool is read-only, potential side effects, rate limits, or authentication details beyond requiring a key.
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?
The description is a single sentence that is front-loaded with the main action, but it is too terse and omits essential details. Every word is earned, but the result is under-specification.
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?
Given the absence of an output schema and two parameters with no descriptions, the description is incomplete. It does not cover input details, return format, or error conditions, making it insufficient for reliable tool invocation.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters1/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 0%, yet the description adds no meaning to the parameters 'key' and 'name'. It does not explain what these parameters represent, their format, or how they relate to the site.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the verb 'list', the resource 'custom domains', and the outcome 'live status (delegated, TLS ready, live)'. It distinguishes this tool from siblings like 'attach_domain' and 'detach_domain'.
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?
The description mentions 'Requires a key' as a prerequisite but provides no guidance on when to use this tool versus alternatives like 'list_sites' or 'get_site'. No exclusions or context are given.
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.
TDQS
A3.7/5.0
Disambiguation5/5
All 14 tools have clearly distinct purposes with no overlap. Related tools like buy_credits, get_balance, and list_topup_packs handle different aspects of credit management without ambiguity.
Naming Consistency5/5
Tool names follow a consistent verb_noun pattern with snake_case (e.g., attach_domain, delete_site, list_sites). No mixing of conventions.
Tool Count5/5
14 tools cover the core functionality of a static site hosting service: domain management, site publishing/deletion, credit system, key acquisition, and name checking. The scope is well-balanced.
Completeness4/5
The tool set covers the main lifecycle (create, read, update, delete) for sites and domains. Minor gaps include no direct tool to rename a site or manage keys beyond creation.