Skip to main content
Glama

devops-linux

terraform_plan_inspect

Inspect Terraform terraform show -json plan output or HCL plan text to count create/update/destroy/replace actions and highlight destructive changes.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "terraform_plan_inspect"
  }
}

Input Schema

NameRequiredDescriptionDefault
textNo
filePathNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full disclosure burden. It does convey real behavior beyond the name: it counts specific action types and flags destructive changes, and the `text`/`filePath` inputs imply pure parsing rather than executing terraform. However, it never states whether the terraform binary is executed, how malformed or non-plan input is handled, or the response shape.

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?

One sentence, front-loaded with the accepted input formats, followed immediately by what is counted and what is highlighted. Nothing is filler and the most decision-relevant information comes first.

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?

With no output schema and no annotations, the description does state enough about the return content (action counts plus destructive highlights) for an agent to know what to expect. The residual gaps—the undocumented `filePath` parameter and error behavior on invalid input—are modest for a two-parameter, read-only 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?

Schema description coverage is 0% for two parameters, so the description must compensate. It distinguishes the two accepted source forms (JSON plan output vs HCL plan text) but never mentions `filePath` at all, leaving one of two parameters entirely undocumented and silent on what happens if both are supplied.

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 names a specific verb (inspect) and a specific resource (Terraform `terraform show -json` plan output or HCL plan text), then enumerates the exact outputs: create/update/destroy/replace counts plus destructive-change highlighting. That level of specificity separates it in practice from siblings like hcl_format_and_validate, though no sibling is named explicitly.

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?

Usage is implied by the stated input types—feed it a plan, not a config file—but there is no explicit when-to-use/when-not guidance and no routing to alternatives such as hcl_format_and_validate for formatting or validation. An agent must infer the boundary itself.

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.

Resources