Set hostname
set_hostnameSet the VPS hostname (valid DNS label; applied on next reboot/rebuild).
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| hostname | Yes | ||
| service_id | Yes |
eqvps
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- First observed
TDQS
A3.6/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description discloses that the hostname is applied on next reboot/rebuild, which is critical behavioral information beyond annotations (none provided). Minor omission: no mention of side effects or required VPS state.
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 with clear front-loading: 'Set the VPS hostname' immediately conveys purpose. No extraneous words.
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?
Adequate for a simple tool with two parameters and no output schema. The description covers the core action and timing but leaves questions about prerequisites and validation rules.
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 coverage is 0%, so description must compensate. It adds 'valid DNS label' for hostname but does not explain service_id (presumably VPS ID). Missing semantics for half the parameters.
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 tool sets a VPS hostname, with a specific verb and resource. It distinguishes from sibling tools which perform different operations like canceling or powering VPS.
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 explicit guidance on when to use this tool versus alternatives like reinstall_vps or power_vps. The description does not mention prerequisites or context, leaving the agent to infer usage.
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.8/5.0
Disambiguation4/5
Tools are cleanly separated into auth, billing, VPS lifecycle, tickets, and delegation, and each maps to a distinct resource/action. A few pairs like set_password vs reset_password and pay_invoice vs topup_balance share surface similarity, but their descriptions draw clear boundaries.
Naming Consistency4/5
Naming is strongly consistent with verb_noun snake_case patterns such as order_vps, list_tickets, and revoke_delegation. Minor deviations are the bare CLI-style verbs login and whoami, plus the slightly awkward topup_balance, but these do not undermine the overall pattern.
Tool Count4/5
27 tools is on the high side, but the server covers several distinct subdomains—account management, billing, VPS operations, support tickets, and delegations—and each tool appears to earn its place. The count is heavy but not unreasonable for the breadth of functionality exposed.
Completeness4/5
Core workflows are covered end-to-end: account creation/login, ordering and provisioning, power/reinstall/cancel, ticket conversations, and delegation management all have the necessary operations. Minor gaps exist, such as no change-password tool, no explicit RDNS/console tool despite delegation mentioning them, and no plan upgrade/downgrade tool.