Skip to main content
Glama

EU Cloud

Find an EU-owned alternative

find_eu_alternative
Read-only

Which EU-owned cloud product (UpCloud, Scaleway, Hetzner, OVHcloud) replaces an AWS, Google Cloud, Azure or DigitalOcean service, and how hard the move is. Examples: "S3", "RDS", "EKS", "DynamoDB", "Cloud Run", "Cosmos DB".

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "service": "<service>"
    },
    "name": "find_eu_alternative"
  }
}

Input Schema

NameRequiredDescriptionDefault
cloudNoSource cloud, if known
serviceYesService name, e.g. "S3" or "Lambda"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so safety and open-world behavior are covered. The description adds genuine value beyond that by disclosing what the answer contains — a replacement recommendation plus how hard the migration is — and by naming the four candidate providers, which no structured field conveys. It does not say how difficulty is judged or whether the mapping is curated versus generated, so it stops short of full disclosure.

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?

Two compact sentences, front-loaded with the actual question the tool answers, followed by an example list. The six-item example list is slightly longer than needed but every item is a distinct, plausible lookup key, so little is wasted.

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 only two parameters, full schema coverage, and no output schema, the description carries the main remaining burden: it explains the shape of the answer (alternative product plus migration difficulty) and the candidate provider set. Gaps are minor — it does not state what happens for a service with no EU equivalent, nor the depth of the migration-difficulty assessment.

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 both parameters are already documented, and the enum on 'cloud' is self-explanatory. The description's example list ("S3", "RDS", "EKS", "DynamoDB", "Cloud Run", "Cosmos DB") modestly extends the schema's single S3/Lambda example by showing cross-cloud inputs, but it does not clarify format, casing, or what to do when the source cloud is unknown.

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?

States a specific mapping task: which EU-owned provider (UpCloud, Scaleway, Hetzner, OVHcloud) replaces a named AWS/GCP/Azure/DigitalOcean service, plus migration difficulty. The examples of accepted service inputs make the resource concrete, and the framing implicitly separates it from the sibling tools that price, cost-estimate, or scan infrastructure rather than map services.

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 by the question framing: you call it when you know a source service and want an EU replacement. There is no explicit when-to-use/when-not guidance and no reference to the siblings (compare_eu_cloud_prices, estimate_cloud_exit_fees, scan_terraform_lock_in), so an agent must infer that this is the discovery step rather than the cost or audit step.

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.