Skip to main content
Glama

Get VPS details

vps_get
Read-only

Get detailed VPS info including live status, config from provider, and subscription status. Passwords are stripped.

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": {
      "id": "<id>"
    },
    "name": "vps_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe VPS ID

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.8/5.0
Behavior4/5

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

The readOnlyHint annotation already establishes this as a safe read, so the bar is lower, and the description still adds genuinely useful behavioral context: "Passwords are stripped" tells the agent to expect redacted credentials rather than a retrieval failure. It stops short of noting that "live status" may involve a provider round-trip or describing error behavior when the VPS is unreachable.

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?

Two short sentences, zero filler, and the substantive content — what is returned — is front-loaded before the redaction caveat. Nothing could be removed without losing information.

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?

For a one-parameter read tool with no output schema, the description does the necessary work by naming the three fields of the response. The only remaining gap is a hint about where to get the ID and what happens if the VPS is missing, which is minor given the simple schema.

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?

With a single parameter and 100% schema description coverage, the schema already documents the required VPS ID and its ObjectId pattern. The description adds nothing about ID provenance (e.g., obtainable from vps_list), so the baseline of 3 applies.

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 uses a specific verb and resource ("Get detailed VPS info") and enumerates the payload's contents: live status, provider config, and subscription status. That distinguishes it from mutating siblings like vps_power and from list-style siblings like vps_list, though it never explicitly names the sibling it is not.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: the mention of "live status" and "subscription status" suggests this is the aggregate overview tool you call when you need more than the list view. There is no explicit when-to-use statement and no guidance on choosing between this and the narrower vps_get_firewall / vps_get_traffic / vps_get_monitoring siblings.

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.