Skip to main content
Glama

get_terraform_snippet

Generate Terraform HCL code to remediate a security risk between a source and target asset based on their relationship type.

Instructions

    Get Terraform code snippet for a specific remediation.

    Args:
        source_name: Name of the source asset
        target_name: Name of the target asset
        relationship_type: Type of relationship (e.g., "CAN_ASSUME", "ALLOWS_TRAFFIC_TO")
        snapshot_id: Optional snapshot ID (default: latest)

    Returns:
        Terraform HCL code snippet for the remediation.
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
source_nameYes
target_nameYes
relationship_typeYes
snapshot_idNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior2/5

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

No annotations exist, so the description carries full burden. It does not disclose behavioral traits such as side effects, auth requirements, or performance implications. The read-only nature is implied but not stated.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise and front-loaded with the purpose. The Args section is structured but includes unnecessary blank lines. Generally efficient.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's simplicity and presence of an output schema, the description is minimally adequate. However, it lacks context on prerequisites (e.g., session snapshot) or what 'remediation' refers to, which could be important for correct invocation.

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 coverage is 0%, but the description provides brief parameter explanations ('Name of the source asset') and default behavior for snapshot_id. This adds basic meaning beyond the schema titles, though not richly detailed.

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 clearly states the tool retrieves a Terraform code snippet for a specific remediation. It identifies the action and resource, distinguishing it from siblings like get_remediations that list remediations, but does not explicitly differentiate.

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?

No guidance on when to use this tool versus alternatives like get_remediations or explain_finding. The description lacks context about prerequisites or typical usage scenarios.

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/cyntrisec/cyntrisec-cli'

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