Skip to main content
Glama

accsly.io VPS and accounts price comparison

VPS host rating

vps_rating
Read-onlyIdempotent

Top of the accsly.io VPS host rating: score 0-10 per host computed from catalog data (price per resource, entry price, trust, terms, tech, reach), with plans count and entry price. Category narrows it: cheap, russia, abroad (ru only), europe, usa, netherlands, germany, vpn (corporate VPN), windows, hourly, crypto (not on ru), game-server, or web-hosting for the shared hosting rating. Empty = overall.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
localeNoLanguage of names and page links; also the price currency: ru = RUB, en = USD, de/es/pt = EUR, tr = TRY.en
categoryNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / category / enum
      Previous value: -[
      -  "",
      -  "cheap",
      -  "russia",
      -  "abroad",
      -  "europe",
      -  "usa",
      -  "netherlands",
      -  "germany",
      -  "vpn",
      -  "windows",
      -  "hourly",
      -  "crypto",
      -  "game-server",
      -  "web-hosting"
      -]New value: +[
      +  "",
      +  "cheap",
      +  "russia",
      +  "abroad",
      +  "europe",
      +  "usa",
      +  "netherlands",
      +  "germany",
      +  "vpn",
      +  "windows",
      +  "hourly",
      +  "crypto",
      +  "game-server",
      +  "dedicated",
      +  "web-hosting"
      +]
  2. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, so the safety burden is lifted; the description adds genuine value by disclosing how the score is derived and that entries include plans count and entry price. It says nothing about ordering guarantees, pagination, or whether limit truncates the ranked list, which is the remaining behavioral gap.

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?

Front-loaded with what the tool returns and how the score is built, then the category semantics. It is a dense run-on with a long enum litany, but nearly every clause carries information an agent needs.

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, so the description must describe returns, and it does: score, plans count, entry price, plus the scoring inputs. Missing are the default cap of 15 / maximum 25 on limit and any ordering/truncation note, which are the only substantive holes for a 3-param read tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With only 33% schema description coverage, the description carries real weight: it explains that category values are topical slices (vpn = corporate VPN, crypto excludes ru, abroad is ru-only) rather than opaque enum strings. The limit parameter is never mentioned, and 'dedicated' appears in the schema enum but is omitted from the prose list, a minor inconsistency.

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 resource (the accsly.io VPS host rating) and what each entry contains: a 0-10 score computed from named criteria, plans count and entry price. It is clearly distinct from siblings like get_vps_host or search_vps by being a ranked aggregate, though it never names those alternatives to make the contrast explicit.

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?

Gives real guidance on the category parameter ('Category narrows it', 'Empty = overall'), which tells the agent how to widen or narrow the result. It stops short of saying when to prefer this ranking over search_vps or compare_hosts, so usage is implied rather than routed.

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