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

mcp-server-terraform

by RajeevSirohi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

tf_output

Retrieve Terraform output values from the current state. Returns all outputs as JSON or a specific output by name.

Instructions

Read Terraform output values from the current state. Returns all outputs as JSON, or a specific output by name.

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_output"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoSpecific output name to retrieve. Omit to get all outputs.
workdirYesAbsolute or relative path to the directory containing .tf files
workspaceNoTerraform workspace to use (default: current workspace)

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?

No annotations exist, so description carries burden. It states it reads state and returns JSON, but does not declare read-only safety, permissions, or potential side effects beyond the implied non-destructive nature.

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?

Two sentences, front-loaded with purpose. No filler, every sentence adds necessary information.

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 tool (3 parameters, no output schema, no annotations), the description covers core functionality, return format, and parameter usage. Slight gap in not mentioning workspace or path handling, but overall complete.

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?

Schema coverage is 100% (baseline 3). Description adds value by explaining the 'name' parameter behavior ('specific output by name') and return format (JSON), which goes beyond schema descriptions.

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 the tool reads Terraform output values from current state, with specific verb 'Read' and resource 'Terraform output values'. It distinguishes from sibling tools (e.g., tf_apply, tf_destroy) which modify state.

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?

Implies the tool is for retrieving outputs, but does not explicitly state when to use it versus siblings like tf_state or tf_resource, nor when not to use it.

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