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

mcp-server-terraform

by RajeevSirohi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

tf_init

Initialize a Terraform working directory by downloading required providers and modules. Run this before planning or applying infrastructure changes.

Instructions

Initialize a Terraform working directory. Downloads providers and modules. Run this before plan or apply on a fresh workspace.

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": {
      "workdir": "<workdir>"
    },
    "name": "tf_init"
  }
}

Input Schema

NameRequiredDescriptionDefault
upgradeNoPass -upgrade to update providers/modules to latest allowed versions
workdirYesAbsolute or relative path to the directory containing .tf files
reconfigureNoPass -reconfigure to reinitialize backend even if already configured

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

With no annotations provided, the description carries the burden of disclosing behavioral traits. It states that the tool 'Downloads providers and modules', which is a key behavior. However, it does not mention other important aspects such as side effects (e.g., creating .terraform directory), idempotency, or permission requirements. The description provides minimal yet adequate transparency for a straightforward init operation.

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 two sentences long, each sentence is informative and front-loaded with the core action. No extraneous words. It earns its place by clearly stating the tool's purpose and usage context.

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?

For a simple init tool with no output schema and 3 parameters fully described in the schema, the description is mostly complete. It explains the tool's role in the Terraform workflow. However, it could mention the creation of the .terraform directory or handling of backend configuration, but the given information suffices for typical usage.

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 description coverage is 100%, so the baseline is 3. The description does not add any parameter-specific meaning beyond the schema, which is acceptable but does not enhance understanding beyond what the schema already provides.

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 'Initialize a Terraform working directory' and 'Downloads providers and modules', giving a specific verb and resource. It also indicates the tool's placement in the workflow ('Run this before plan or apply on a fresh workspace'), distinguishing it from siblings like tf_plan or tf_apply which are not initialization operations.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly advises when to run this tool ('before plan or apply on a fresh workspace'), providing clear context for usage. However, it does not mention when not to use it or compare it to other siblings like tf_validate or tf_workspace, but the guidance is sufficient for the primary use case.

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