vps-mcp

Official

Overview Schema Source Related Servers Discussions Admin

get_domain

Retrieve detailed information about a specific domain by providing its UUID. Get domain details including DNS records, status, and configuration.

Instructions

Get detailed information about a specific domain.

Args: domain_uuid: The UUID of the domain

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": {
      "domain_uuid": "<domain_uuid>"
    },
    "name": "get_domain"
  }
}

Input Schema

Name	Required	Description	Default
`domain_uuid`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jun 13, 2026

TDQS

B3.3/5.0

Behavior2/5

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

No annotations are present, so the description must disclose behavioral traits. It does not mention that the operation is read-only, any authentication requirements, rate limits, or what happens if the domain does not exist. The description is insufficient for transparency.

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?

The description is extremely concise: two sentences (purpose + args). It is front-loaded with the core purpose and contains no fluff. Every word earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the simplicity of the tool (one required parameter, output schema present), the description adequately covers the essentials. However, a brief note about UUID format or error conditions would improve completeness.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, and the description adds only 'The UUID of the domain' for domain_uuid, which barely extends beyond the schema's title 'Domain Uuid' and type. No format, constraints, or additional context are provided.

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 states 'Get detailed information about a specific domain,' which clearly identifies the verb and resource. It distinguishes from siblings like list_domains and search_domains by focusing on a single domain via UUID.

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?

No guidance is provided on when to use this tool versus alternatives (e.g., search_domains, list_domains). The need for a domain_uuid is implied but not explicitly stated as a prerequisite.

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