Skip to main content
Glama
Sign In
Terraform Engine MCP Server

Terraform Engine MCP Server

by asadongit
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

get_deployment_status

Retrieve the current status, configurations, and outputs of a specific deployment by name.

Instructions

Get the current status, configurations, and outputs of a deployment by its name.
Args:
    deployment_name: The unique name of the deployment to inspect.

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

Input Schema

NameRequiredDescriptionDefault
deployment_nameYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

No annotations provided. Description implies a read-only operation but does not disclose error handling (e.g., if deployment not found) or permissions needed. Basic transparency is present.

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?

Extremely concise: one sentence plus an Args line. Purpose is front-loaded. No wasted words.

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?

Given the tool's simplicity, the description covers the basics but lacks integration hints (e.g., check status before destroy) and error scenarios. Output schema is external but not referenced.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Single parameter 'deployment_name' has 0% schema coverage, but description adds meaning: 'the unique name of the deployment to inspect'. This compensates well for the trivial parameter type.

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?

Description clearly states 'Get the current status, configurations, and outputs of a deployment by its name', specifying both the verb (Get) and the resource (deployment), distinguishing it from siblings like list_tasks and destroy_deployment.

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 explicit guidance on when to use this tool vs alternatives (e.g., before destroy_deployment) or prerequisites. Only states 'by its name' without contextual cues.

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