Skip to main content
Glama
Sign In
Terraform Engine MCP Server

Terraform Engine MCP Server

by asadongit
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

destroy_deployment

Tear down and delete an existing deployment by providing its name.

Instructions

Tear down and delete an existing deployment by its name.
Args:
    deployment_name: The name of the deployment to destroy.

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": {
      "deployment_name": "<deployment_name>"
    },
    "name": "destroy_deployment"
  }
}

Input Schema

NameRequiredDescriptionDefault
deployment_nameYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations, the description must fully disclose behavior but only states the action. It omits critical details such as whether the deletion is irreversible, what happens to associated resources, and required permissions. For a destructive tool, this is insufficient.

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?

The description is extremely concise with two sentences, no redundant information, and front-loads the core action. Every word earns its place.

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

Completeness2/5

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

Given the tool is destructive and has no annotations, the description is too sparse. It lacks essential context such as irreversibility, impact on related resources, and failure conditions. The existence of an output schema does not compensate for missing safety information.

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 description adds meaning to the single parameter by stating its role ('the name of the deployment to destroy'), which goes beyond the schema's bare name. However, it does not clarify format, validation rules, or error conditions.

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 clearly states the verb (tear down, delete) and the resource (deployment), with the key identifier (by name). It effectively distinguishes from sibling tools like provision_task (create) and get_deployment_status (check status).

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?

No guidance on when to use this tool versus alternatives, no prerequisites, and no warnings about irreversible effects. The agent is left to infer usage context without explicit direction.

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

Deploy Server

Other Tools