Skip to main content
Glama
Sign In
ansible-mcp-server

ansible-mcp-server

by washyu
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

terraform-plan

Generate an execution plan for Terraform infrastructure changes, showing what will be created, modified, or destroyed before applying.

Instructions

Create an execution plan for Terraform changes

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

Input Schema

NameRequiredDescriptionDefault
directoryYesDirectory containing Terraform configuration
destroyNoPlan to destroy resources
targetNoResource to target for planning
varFileNoPath to variables file
varsNoVariables to pass to Terraform

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/5.0
Behavior2/5

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

Given no annotations, the description must convey behavioral traits. It only states 'create an execution plan' without noting that this is read-only, non-destructive, or that it checks for changes. Key behaviors like output format or state handling are missing.

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?

The description is a single concise sentence with no fluff. It front-loads the action and resource, but could benefit from additional details without becoming verbose. Still efficient.

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?

The description lacks essential context: no indication of return value (the plan itself), no mention of idempotency, locking, or dependencies. For a complex tool with 5 parameters, this is insufficient.

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 coverage is 100%, with all 5 parameters described in the input schema. The description adds no additional meaning beyond what the schema provides, so baseline score of 3 is appropriate.

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 'Create an execution plan for Terraform changes' uses a specific verb ('Create') and resource ('execution plan for Terraform changes'), clearly distinguishing it from sibling tools like terraform-apply (applies the plan) and terraform-output (shows outputs).

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 is provided on when to use this tool versus alternatives, such as prerequisites (e.g., terraform init) or scenarios where terraform-plan is inappropriate. The description is purely functional without contextual usage advice.

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