Skip to main content
Glama

EU Cloud

Scan Terraform for cloud lock-in

scan_terraform_lock_in
Read-only

Takes the contents of Terraform (.tf) files as text and lists the AWS, Google Cloud, Azure and DigitalOcean services used, how portable each is to EU-owned clouds, what replaces it, and an EU portability score. The text is scanned in memory and not stored. Remove secrets before sending.

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": {
      "terraform": "<terraform>"
    },
    "name": "scan_terraform_lock_in"
  }
}

Input Schema

NameRequiredDescriptionDefault
terraformYesContents of one or more .tf files, joined

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 only declare readOnlyHint=true and openWorldHint=false. The description adds genuinely new behavior: the text is 'scanned in memory and not stored', plus a security caveat about stripping secrets. That is exactly the kind of data-handling context annotations cannot convey. It does not mention the 200,000-character input ceiling or throughput limits, which keeps it from a 5.

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?

Three short sentences: what it does, where the data goes, and a safety instruction. Front-loaded with the purpose, no filler, and the warning placed last where it belongs.

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

Completeness5/5

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

With one required parameter, no output schema, and light annotations, the description covers what an agent needs: input form, privacy behavior, and an explicit list of what comes back. Nothing material is missing for a single-input analysis tool.

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?

There is a single parameter with 100% schema description coverage ('Contents of one or more .tf files, joined'), so the schema already carries the semantics and the baseline is 3. The description's 'Remove secrets before sending' adds a small amount of practical meaning about what belongs in that string, but no format or multi-file joining guidance beyond the schema.

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 opens with a concrete verb plus resource ('Takes the contents of Terraform (.tf) files as text and lists the AWS, Google Cloud, Azure and DigitalOcean services used') and even enumerates the outputs: portability, replacements, and a score. That is far more specific than a tautology. It stops short of a 5 because it never contrasts itself with siblings such as find_eu_alternative, which also promises 'what replaces it'.

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?

Use is implied — you send .tf file contents to learn how locked-in you are — and there is a real preparation instruction ('Remove secrets before sending'). But nothing says when to choose this over find_eu_alternative or compare_eu_cloud_prices, and no exclusions are stated.

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.