Specky

Validate Infrastructure as Code

sdd_validate_iac

Read-onlyIdempotent

Generates and routes validation payloads for Terraform or Azure infrastructure code. Use to validate IaC against specs across cloud providers.

Instructions

Generates a validation payload for Terraform MCP (plan/validate) or Azure MCP (template validation). The AI client routes this payload to the appropriate MCP server for execution.

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

Input Schema

Name	Required	Description	Default
`cloud`	No	Target cloud provider	azure
`iac_dir`	No	Directory containing IaC files to validate. Defaults to feature directory
`provider`	No	IaC provider to use	terraform
`spec_dir`	No	Spec directory path (relative to workspace root)	.specs
`feature_number`	No	Feature number (zero-padded, e.g. '001')	001

Schema Changelog

Changes observed during successful MCP inspections.

First observedv3.4.0-rc.14May 3, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, destructiveHint, idempotentHint, and openWorldHint, indicating a safe, non-destructive operation. The description adds that the tool generates a payload and does not execute validation, which is consistent but only marginally extends transparency beyond annotations.

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, front-loads the core purpose, and contains no redundant information. Every sentence adds value.

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?

Given the tool generates a payload for external execution, the description covers the essential purpose and routing. However, it lacks hints about the output format (e.g., JSON structure) since no output schema is provided, leaving a minor gap.

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?

The input schema covers all 5 parameters with descriptions and defaults, achieving 100% coverage. The description does not add any additional meaning beyond what the schema provides, so baseline 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 uses a specific verb ('Generates a validation payload') and clearly identifies the resource and purpose, distinguishing it from sibling tools like sdd_generate_iac (which creates IaC) and sdd_validate_ears.

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?

The description mentions that the payload is routed to a specific MCP server but does not explicitly state when to use this tool versus alternatives or provide exclusion criteria. It implies usage context but lacks direct guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server