Skip to main content
Glama

EU Cloud

Estimate cloud exit fees

estimate_cloud_exit_fees
Read-only

Egress cost of moving data out of AWS, Azure or Google Cloud at list price, whether the provider's exit program waives it and its conditions, and what the EU Data Act allows.

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": {
      "provider": "<provider>",
      "data_gb": "<data_gb>"
    },
    "name": "estimate_cloud_exit_fees"
  }
}

Input Schema

NameRequiredDescriptionDefault
data_gbYesData to move, in GB (1 TB = 1000 GB)
providerYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover safety (readOnlyHint=true) and the open-ended lookup nature (openWorldHint=true), so the bar is lower. The description adds real behavioral context beyond that: the number is a list-price figure (not a negotiated/actual bill), it also reports waiver eligibility and the conditions attached, and it frames results in regulatory terms. It stops short of noting currency, pricing-date volatility, or that list prices change.

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?

One dense sentence that front-loads the core computation before the secondary waiver and regulatory facets. No filler, no restatement of the tool name, and every clause adds a distinct deliverable.

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?

There is no output schema, so the description must carry the return shape — and it does, listing cost, waiver status with conditions, and the EU Data Act answer. For a 2-parameter read-only tool that is close to sufficient; only the units/currency of the returned figure and pricing recency are left unstated.

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?

With 2 parameters at 50% schema description coverage, only data_gb is documented (in the schema, including the GB vs TB convention); provider has an enum but no described semantics. The description contributes no parameter-level meaning at all — nothing about what 'list price' implies for the inputs or whether providers have per-request minimums. Adequate only because the parameter set is tiny and the enum is self-explanatory.

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?

The description names a concrete resource (egress cost of moving data out of AWS/Azure/GCP) and enumerates the three things returned: list-price cost, whether the provider's exit program waives it plus conditions, and the EU Data Act position. That multi-facet scope is sharply distinct from the siblings (price comparison, alternative-finder, Terraform lock-in scan), so an agent can route without opening the schema.

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 only implied: the phrasing 'moving data out of' plus the Data Act angle signals a pre-migration / lock-in assessment task. There is no explicit when-to-use statement, no exclusion (e.g. 'not for intra-region transfer'), and no mention of the sibling tools it competes with.

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.