Skip to main content
Glama

Generate Infrastructure as Code

sdd_generate_iac
Idempotent

Reads DESIGN.md to generate Terraform or Bicep infrastructure code, including variables and a topology diagram.

Instructions

Reads DESIGN.md to detect infrastructure needs and generates Terraform or Bicep files. Returns generated file contents, variables, and a Mermaid diagram of the infrastructure topology.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
feature_numberNoFeature number (zero-padded, e.g. '001')001
spec_dirNoSpec directory path (relative to workspace root).specs
providerNoIaC provider to useterraform
cloudNoTarget cloud providerazure
modulesNoSpecific infrastructure modules to generate (e.g., 'networking', 'compute', 'database'). If omitted, generates all detected from DESIGN.md
Behavior4/5

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

IdempotentHint clarifies safe to retry; description details output (files, variables, diagram) aligning with read-only generation.

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 concise sentences with no fluff; front-loaded verb and resource.

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?

Covers input source, output contents, and diagram generation; lacks error conditions but adequate for generation 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 covers 100% of parameter descriptions; description adds no extra parameter meaning beyond existing schema.

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 DESIGN.md and generates Terraform or Bicep files, distinguishing it from siblings like sdd_validate_iac.

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 use after DESIGN.md exists, but no explicit guidance on when to use vs alternatives like sdd_generate_all_docs.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/paulasilvatech/specky'

If you have feedback or need assistance with the MCP directory API, please join our Discord server