list_sites
List the sites owned by this key (name, live URL, updated time). Requires a key.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| key | Yes | boom_sk_ key. |
boomurl
by com.boomurl
TDQS
B3.2/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, and description does not disclose any behavioral traits such as read-only, side effects, rate limits, or error handling.
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?
Single sentence, front-loaded with primary action, no wasted words.
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?
Missing output schema; description gives only a hint of return fields but lacks details on format, pagination, or error conditions. For a list tool with no annotations, more context is needed.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters3/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% with description of the key parameter. Description adds no extra meaning beyond the schema, so baseline score of 3 is appropriate.
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?
Clearly states verb 'List', resource 'sites', and scope 'owned by this key'. Provides hint about returned fields (name, live URL, updated time).
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?
Only states 'Requires a key' but does not explain when to use this tool versus siblings like get_site or list_domains.
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.