Skip to main content
Glama

accsly.io VPS and accounts price comparison

Search VPS plans

search_vps
Read-onlyIdempotent

Find VPS/VDS (or shared hosting, dedicated) plans across 2,000+ hosts by country, RAM/CPU/disk minimums, disk type, monthly budget, payment method, hourly billing and task presets. Returns 10 plans per page, cheapest first by default, each with specs, monthly price, payment methods, the host page and an order link. Prices are read on the hosts' own sites and refreshed hourly.

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": "search_vps"
  }
}

Input Schema

NameRequiredDescriptionDefault
osNolinux, windows, freebsd, iso (own ISO image).
hostNoOnly this host (slug, domain or name).
kindNovps, hosting (shared web hosting) or dedicated servers.vps
pageNo
sortNoprice, price_desc, ram_value (cheapest per GB RAM), cpu_value (per core), disk_value (per GB disk), ram, disk, ghz.price
taskNoPreset filter for a typical job: vpn (corporate VPN), site, bot, games, windows, docker, storage, proxy, parsing, db, mail, dev, ai, or a game server (game-minecraft, game-cs2, game-rust…).
textNoFree text over plan and host names, e.g. "ryzen", "timeweb nvme".
hourlyNoOnly plans billed by the hour.
localeNoLanguage of names and page links; also the price currency: ru = RUB, en = USD, de/es/pt = EUR, tr = TRY.en
ram_gbNoMinimum RAM, GB.
regionNoabroad = outside Russia, eu, cis, asia, america.
countryNoISO 3166-1 alpha-2 codes of server locations (any of them), e.g. ["DE","NL"].
cpu_ghzNoMinimum core frequency, GHz.
disk_gbNoMinimum disk, GB.
landingNoSlug of a ready-made selection whose filter to use, e.g. "for-docker", "germany", "nvme-netherlands", "pay-with-sbp", "web-hosting-wordpress". Explicit arguments override it.
optionsNoRequired features (all of them): ipv6, ddos, trial, moneyback, smtp (port 25), api, instant, gpu, win_license, panel, no_kyc, ru_support, rub.
paymentNoAccepted payment methods (any of them): card_ru (Russian MIR card), sbp, card_world (non-Russian card), crypto, yoomoney, webmoney, paypal, invoice.
cpu_coresNoMinimum vCPU cores.
disk_typeNossd = SSD or NVMe, nvme = NVMe only, hdd.
max_priceNoMaximum price per month in the locale currency (RUB for ru, USD for en, EUR for de/es/pt, TRY for tr).
one_per_hostNoAt most one plan per host.
virtualizationNo
unlimited_trafficNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / country / items / enum
      Previous value: -[
      -  "RU",
      -  "NL",
      -  "DE",
      -  "FI",
      -  "US",
      -  "PL",
      -  "FR",
      -  "GB",
      -  "KZ",
      -  "TR",
      -  "LV",
      -  "EE",
      -  "LT",
      -  "SE",
      -  "CH",
      -  "CZ",
      -  "BG",
      -  "MD",
      -  "RO",
      -  "AT",
      -  "ES",
      -  "IT",
      -  "GR",
      -  "HU",
      -  "SK",
      -  "RS",
      -  "BE",
      -  "DK",
      -  "NO",
      -  "IE",
      -  "IS",
      -  "PT",
      -  "HR",
      -  "SI",
      -  "ME",
      -  "MK",
      -  "AL",
      -  "CY",
      -  "UA",
      -  "BY",
      -  "AM",
      -  "GE",
      -  "UZ",
      -  "KG",
      -  "IL",
      -  "AE",
      -  "HK",
      -  "SG",
      -  "JP",
      -  "KR",
      -  "CN",
      -  "IN",
      -  "ID",
      -  "MY",
      -  "TH",
      -  "PK",
      -  "AU",
      -  "CA",
      -  "MX",
      -  "BR",
      -  "AR",
      -  "CL",
      -  "CO",
      -  "PE",
      -  "EC",
      -  "BO",
      -  "CR",
      -  "GT",
      -  "PR",
      -  "ZA",
      -  "LU",
      -  "LI",
      -  "BA",
      -  "TW",
      -  "VN",
      -  "PH",
      -  "KH",
      -  "MM",
      -  "BD",
      -  "NP",
      -  "SA",
      -  "QA",
      -  "BH",
      -  "KW",
      -  "OM",
      -  "IQ",
      -  "EG",
      -  "NG",
      -  "NZ",
      -  "AQ",
      -  "AZ",
      -  "MT",
      -  "LA",
      -  "IR",
      -  "LB",
      -  "PA",
      -  "PY",
      -  "UY",
      -  "CW",
      -  "KE",
      -  "CG",
      -  "MA",
      -  "GH"
      -]New value: +[
      +  "RU",
      +  "NL",
      +  "DE",
      +  "FI",
      +  "US",
      +  "PL",
      +  "FR",
      +  "GB",
      +  "KZ",
      +  "TR",
      +  "LV",
      +  "EE",
      +  "LT",
      +  "SE",
      +  "CH",
      +  "CZ",
      +  "BG",
      +  "MD",
      +  "RO",
      +  "AT",
      +  "ES",
      +  "IT",
      +  "GR",
      +  "HU",
      +  "SK",
      +  "RS",
      +  "BE",
      +  "DK",
      +  "NO",
      +  "IE",
      +  "IS",
      +  "PT",
      +  "HR",
      +  "SI",
      +  "ME",
      +  "MK",
      +  "AL",
      +  "CY",
      +  "UA",
      +  "BY",
      +  "AM",
      +  "GE",
      +  "UZ",
      +  "KG",
      +  "TJ",
      +  "IL",
      +  "AE",
      +  "HK",
      +  "SG",
      +  "JP",
      +  "KR",
      +  "CN",
      +  "IN",
      +  "ID",
      +  "MY",
      +  "TH",
      +  "PK",
      +  "AU",
      +  "CA",
      +  "MX",
      +  "BR",
      +  "AR",
      +  "CL",
      +  "CO",
      +  "PE",
      +  "EC",
      +  "BO",
      +  "CR",
      +  "GT",
      +  "PR",
      +  "ZA",
      +  "MU",
      +  "LU",
      +  "LI",
      +  "BA",
      +  "TW",
      +  "VN",
      +  "PH",
      +  "KH",
      +  "MM",
      +  "BD",
      +  "NP",
      +  "SA",
      +  "QA",
      +  "BH",
      +  "KW",
      +  "OM",
      +  "IQ",
      +  "EG",
      +  "NG",
      +  "NZ",
      +  "AQ",
      +  "AZ",
      +  "MT",
      +  "LA",
      +  "IR",
      +  "LB",
      +  "PA",
      +  "PY",
      +  "UY",
      +  "CW",
      +  "KE",
      +  "CG",
      +  "MA",
      +  "GH"
      +]
  2. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world). The description adds genuinely non-structured behavior: page size of 10, cheapest-first default ordering, per-result payload contents, and a data-freshness disclosure that prices are scraped from host sites and refreshed hourly — a real caveat an agent could not derive from annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, front-loaded with the verb and scope, then results, then data provenance. The first sentence is heavily packed with a long feature list, but every clause maps to a real parameter group and nothing is filler.

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?

With 23 optional parameters and no output schema, the return-shape sentence (10 plans per page, specs, monthly price, payment methods, host page, order link) does important work. Coverage of pagination limits and the zero-required-parameter nature is left to the schema, which is acceptable; what an agent needs to call this correctly is present.

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 coverage is 87%, so the baseline is 3; the schema already documents sort modes, task presets, locale-currency mapping, and option/payment enums. The description only restates those parameter groups at a high level (country, RAM/CPU/disk minimums, disk type, budget, payment, hourly, presets) without adding syntax, interaction, or precedence detail beyond the landing-override note.

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 ("Find VPS/VDS ... plans across 2,000+ hosts") and enumerates the filter axes, so the agent knows this is the broad catalog search. It does not name or contrast the siblings (compare_hosts, list_offers, vps_rating), which is the only gap at this dimension.

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 implied rather than stated: it is clearly the discovery tool, and the landing parameter note ("Explicit arguments override it") is a useful precedence rule. There is no explicit when-to-use-this-vs-siblings guidance and no when-not guidance, leaving the agent to infer that scoring/comparison belongs to compare_hosts or vps_rating.

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