Skip to main content
Glama

VPS plans, filtered

vps_plans
Read-onlyIdempotent

VPS plans as /prices/vps/plans and GET /v1/vps/plans return them: the very same function, so the answers cannot differ for the same filters. Every row is a plan with its verified list price a month (excl. VAT) for the chosen contract term, all price points the provider states, buying facts (IPv4, traffic, disk and vCPU type; null = not stated), region (region_stated=false when the source names none), verified_at and source_url. Only plans with a price verified in the last 3 days carry a price; the others are listed apart in not_verified without one. Sorted by price (or per GB RAM, per vCPU); nothing is ranked for money. Each plan has a detail_url with its facts sheet. Answer pages for common searches: /prices/vps/cheapest.

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_plans"
  }
}

Input Schema

NameRequiredDescriptionDefault
ipv4NoOnly plans whose source states an own IPv4 address is included
nvmeNoOnly plans whose source states NVMe disks
sortNoSort orderprice
termNoContract term: none = no commitment (default), 12 = up to 12 months, anynone
vcpuNoMinimum vCPU
limitNoMaximum plans returned, 1 to 500 (the same rows as the API; the API default is 200)
ram_gbNoMinimum RAM in GB
regionNoA place key: eu, us, asia, a country code such as de or nl, or none (plans whose source states no region)
disk_gbNoMinimum disk in GB
currencyNoeur (default) or usdeur
providerNoProvider slugs, e.g. hetzner
dedicatedNoOnly plans whose source states dedicated vCPUs
max_priceNoMaximum price a month in the chosen currency
traffic_tbNoMinimum included traffic in TB a month (unlimited counts)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered; the description goes further by disclosing the crucial data-quality rule that only plans priced within the last 3 days carry a price and the rest appear separately in not_verified without one. It also explains null semantics ('null = not stated') and the region_stated=false flag, which an agent could not infer from the annotations. It stops short of describing response envelope or pagination behavior.

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 body is dense but organized, moving from rows to price-verification caveats to sorting to detail_url. However, the opening clause about the web page and GET /v1/vps/plans being 'the very same function, so the answers cannot differ for the same filters' is defensive meta-commentary that does not help an agent select or invoke the tool, and the trailing '/prices/vps/cheapest' fragment reads as an afterthought.

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 14-parameter, no-output-schema read tool, the description covers the important ground: what a row contains, the price-verification window, the not_verified bucket, sorting options, and where to get more detail via detail_url. Gaps are minor, mainly the absence of guidance on which sibling tool handles cost estimation or single-plan lookup.

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 carries the per-parameter meaning and the baseline applies. The description adds a little beyond it, notably that prices are for the chosen contract term and that sorting can be by price, per GB RAM, or per vCPU, but it does not elaborate on the interplay of filters or on the 1-500 limit range.

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 states a specific resource (VPS plans) and describes exactly what each returned row contains: price per month excl. VAT, IPv4/traffic/disk/vCPU facts, region, verified_at and source_url. It never names a sibling tool (cheapest_for_spec, search_skus, estimate_cost, get_price) so an agent cannot tell from the text alone why it would pick this over those, which keeps it below a 5.

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?

There is no explicit statement of when to use this tool versus the sibling tools that also deal with prices and specs. The only usage-adjacent sentence, 'Answer pages for common searches: /prices/vps/cheapest', is a cryptic URL fragment that does not tell the agent when to prefer this call or when to exclude it.

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.

Resources