Skip to main content
Glama

EU Cloud

Compare cloud prices

compare_eu_cloud_prices
Read-only

Monthly EUR list prices for the same server, database, Kubernetes and storage baskets on AWS, Azure, Google Cloud, UpCloud, Hetzner, Scaleway and OVHcloud, refreshed monthly from provider price APIs.

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

Input Schema

NameRequiredDescriptionDefault
basketNoFilter, e.g. "4 vCPU", "postgres", "kubernetes". Omit for all baskets

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=true and openWorldHint=true, so the safety profile is covered. The description adds genuinely useful traits beyond that: prices are list prices (not negotiated discounts), denominated in EUR, billed monthly, sourced from provider price APIs, and refreshed on a monthly cadence. It still omits return shape and whether all providers are always compared, but the freshness and pricing-basis disclosures are exactly the kind of context annotations cannot express.

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?

One dense sentence with no filler; the currency, scope and provider list are front-loaded. It loses a point because the sentence is entirely a noun phrase, so the action the tool performs is never stated outright and the agent must reconstruct it.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only, single-optional-parameter tool with annotations and no output schema, the essential context (currency, cadence, data source, pricing basis) is present. What is missing is enough about the response to reason about the result: whether it returns one price per provider per basket, a comparison table, or only providers where the basket exists, and whether the eight providers are always covered.

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?

The single optional 'basket' parameter is fully documented in the schema (100% coverage, with examples and an omit-for-all instruction), so the schema carries the burden. The description's mention of 'baskets' adds only conceptual framing about what a basket contains (server, database, Kubernetes, storage) and no filtering syntax or behavior beyond that, matching the baseline for high schema coverage.

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 names a precise resource: monthly EUR list prices for server, database, Kubernetes and storage baskets across eight named providers. The scope is specific enough that an agent can distinguish it from siblings like estimate_cloud_exit_fees or find_eu_alternative, though the phrasing is a bare noun phrase with no explicit verb, so the agent must infer that the tool returns a cross-provider comparison rather than, say, a catalog.

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 when-to-use or when-not-to-use guidance and no routing to alternatives. The only implicit constraint is 'refreshed monthly', which hints the data is not real-time, but nothing tells the agent whether to prefer this over find_eu_alternative or scan_terraform_lock_in when the underlying question is about migrating or lock-in.

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.