Skip to main content
Glama

Get VPS prices

vps_get_pricing
Read-only

Get VPS component sell prices grouped by hostsystem. Shows per-component price per step, min/max limits, included free tier amounts, and yearly discount. Supports currency conversion (EUR/USD) and gross/net display. Pass resource amounts (core, mem, etc.) with a hostsystem to calculate the total price for a configuration.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "vps_get_pricing"
  }
}

Input Schema

NameRequiredDescriptionDefault
hddNoHDD storage in GB (multiples of 10)
memNoRAM in GB
coreNoNumber of CPU cores
ipv4NoNumber of IPv4 addresses
nvmeNoNVMe storage in GB (multiples of 10)
backupNoNumber of backup slots
displayNoPrice display mode (default: gross)
networkNoNetwork speed in Mbit/s (multiples of 1000)
currencyNoCurrency for prices (default: EUR)
hostsystemNoHostsystem identifier for price calculation (e.g. de_epyc). Required when passing resource amounts.

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4/5.0
Behavior4/5

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

readOnlyHint=true already establishes this is a safe read, and the description still adds real value: it discloses what is returned (per-step per-component price, min/max limits, included free tier, yearly discount) and behavior (EUR/USD conversion, gross/net display). It omits error behavior for an unknown hostsystem and says nothing about response shape/pagination, which is minor given a read-only lookup.

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?

Four tight sentences with no filler: the output content first, then display/currency options, then the calculation mode. The most decision-relevant information (what it returns and how to get a configuration total) is front-loaded and nothing is repeated verbatim.

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?

No output schema exists, and the description does carry the burden of explaining return values, which it does concretely. With 10 optional parameters, all schema-documented, and no destructive behavior, the only remaining gap is how partial resource amounts are handled (e.g., omitted fields default to zero or to minimums).

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 all ten parameters, including both enums, are already documented; baseline is 3. The description only gestures at parameter meaning with '(core, mem, etc.)' and restates the hostsystem dependency that the schema already spells out ('Required when passing resource amounts'). It adds little semantic information the schema lacks.

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?

States a specific verb and resource: 'Get VPS component sell prices grouped by hostsystem', which is a level of detail beyond the generic title 'Get VPS prices'. It implicitly separates itself from get_domain_pricing by scoping to VPS components, but never names a sibling or explicitly excludes alternatives.

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

Usage Guidelines4/5

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

The final sentence supplies concrete usage guidance, splitting the two modes: bare calls to list component pricing, or passing resource amounts plus a hostsystem to compute a configuration total. It does not state when to prefer a different pricing tool, which keeps it below a 5.

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.