mcp_ruvds.com

ruvds_list_tariffs

Retrieve available VPS tariffs, drive tariffs, and payment period discounts. Use returned tariff IDs to create a new server.

Instructions

List VPS tariffs, drive tariffs, payment_period_discount (e.g. period 3=5% off, 5=20% off). Use tariff IDs in create_server.

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

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 30, 2026

TDQS

A4.2/5.0

Behavior3/5

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

No annotations provided, so description carries full burden. It lists the types of tariffs but does not disclose details like pagination, ordering, or rate limits. For a zero-parameter read-only list, this is adequate but lack of any behavioral flags is a minor gap.

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 sentences, front-loaded with purpose and a useful usage hint. No unnecessary words.

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 simple list tool with no parameters and no output schema, the description is fairly complete. It tells what is listed and how to use the results. Lacks example output format but not critical. Sibling tools are diverse, and this stands out.

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?

There are zero parameters, so schema coverage is trivially 100%. Description adds no parameter info because none exist. Baseline score of 4 is appropriate as description adds no additional meaning beyond schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description clearly states it lists VPS tariffs, drive tariffs, and discounts. It also explains the purpose of tariff IDs in creating servers, distinguishing it from sibling list tools like list_servers or list_datacenters.

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?

Description explicitly states to use tariff IDs in create_server, providing clear usage context. However, it does not explicitly mention when not to use this tool or name alternatives, but the context is strong enough.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.