Skip to main content
Glama
Sign In
ukraine.com.ua MCP

ukraine.com.ua MCP

by sanyo4ever
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

adm_hosting_sites

Retrieve a list of sites and subdomains associated with a hosting account. Filter by site ID or paginate results.

Instructions

List sites and subdomains for a hosting account

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "account_id": "<account_id>"
    },
    "name": "adm_hosting_sites"
  }
}

Input Schema

NameRequiredDescriptionDefault
account_idYesHosting account ID
virtual_domain_idNoOptional site ID filter
pageNoResult page, defaults to 1

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior2/5

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

No annotations are provided, so the description bears full responsibility for behavioral transparency. It merely states it lists, implying a read operation, but discloses no other behavioral traits such as authentication needs, pagination behavior, or return format.

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 very concise at one sentence, but it lacks necessary details for effective use. It is front-loaded with the verb, but the brevity sacrifices completeness.

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 complexity of 3 parameters, no output schema, and no annotations, the description is incomplete. It does not explain pagination, filter usage, or return values, leaving an agent insufficiently informed.

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 description coverage is 100%, so the schema already documents all parameters. The description adds no additional meaning beyond what is in the schema, meeting the baseline of 3.

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 clearly states it lists sites and subdomains for a hosting account, using a specific verb and resource. It distinguishes from siblings like adm_hosting_accounts (lists accounts) and adm_hosting_webapp_info (info about webapps), but does not explicitly differentiate.

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 provides no guidance on when to use this tool versus alternatives. It does not mention that it requires an account_id or that it can filter by virtual_domain_id, nor does it contrast with sibling tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools