Skip to main content
Glama

devops-linux

hcl_format_and_validate

Format Terraform/Packer HCL blocks with standard 2-space indentation, aligned = assignments, and balanced-brace syntax validation.

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

Input Schema

NameRequiredDescriptionDefault
textNo
filePathNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses the formatting rules and that brace-balance validation occurs, which is real behavioral content. However, it never says whether a supplied filePath causes the file on disk to be rewritten or whether the tool is purely a text transformer, nor how validation failures are surfaced — a serious omission for a tool whose name includes 'validate'.

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?

A single front-loaded sentence with no filler; every clause (indentation, alignment, brace validation) carries distinct information. Nothing is padded or repeated.

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?

For a two-parameter tool with no annotations and no output schema, the description should at minimum explain the text vs. filePath choice and what happens on invalid syntax. Neither is covered, so an agent cannot reliably call it without guessing.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate, and it does not: neither 'text' nor 'filePath' is mentioned. In particular the relationship between the two parameters (which wins if both are provided, whether filePath reads or writes) is left entirely unexplained. The formatting details describe output, not inputs.

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 concrete verb+resource pair (format HCL blocks) and even specifies the output style: 2-space indentation, aligned '=' assignments, brace-balancing validation. An agent can tell this is a formatting/linting tool rather than a plan inspector like terraform_plan_inspect. It stops short of explicitly differentiating itself from siblings, but the purpose is unambiguous.

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?

There is no when-to-use or when-not-to-use guidance, no mention of prerequisites, and no named alternative. The agent must infer that this applies to HCL/Terraform/Packer content, which is stated, but nothing tells it when formatting is or isn't appropriate.

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