Terraform Engine MCP Server

Overview Schema Source Related Servers Discussions Admin

list_tasks

Browse Terraform task templates in the registry, filtered by category or provider, to discover reusable infrastructure deployments.

Instructions

List all available Terraform tasks (templates) in the registry.
Args:
    category: Optional category to filter tasks (e.g. database, network, compute).
    provider: Optional cloud provider to filter tasks (e.g. aws, azure, gcp).
Returns:
    JSON string representing the list of tasks and their details.

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

Input Schema

Name	Required	Description	Default
`category`	No
`provider`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 30, 2026

TDQS

A4.2/5.0

Behavior4/5

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

No annotations are provided, so the description bears full burden. It discloses that the tool returns a JSON string and supports optional filtering, which implies a read-only operation. However, it does not explicitly confirm idempotency or safety, though 'list' implies no side effects.

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 extremely concise with three clear sections: purpose, Args, Returns. Every sentence adds value, and the structure is front-loaded with the primary action. No unnecessary words.

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 an output schema exists (though not detailed here), the description adequately covers the return type ('JSON string') and parameter purposes. It does not mention error handling or empty results, but for a list operation with simple filtering, this is sufficient.

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 description coverage is 0% per context, but the description adds meaning to both parameters: it explains they are optional filters and provides examples (e.g., 'database, network, compute' for category; 'aws, azure, gcp' for provider). This goes beyond the schema's type and title alone.

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 clearly states 'List all available Terraform tasks (templates) in the registry.' The verb 'list' and resource 'Terraform tasks' are specific, and the scope 'registry' is provided. It distinguishes from siblings like provision_task (deploy) and get_task_schema (schema retrieval).

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 indicates optional filters (category, provider) but does not explicitly state when to use this tool relative to alternatives. It lacks guidance on prerequisites or situations where listing is appropriate. The sibling names imply differentiation, but the description itself offers no usage context.

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

Deploy Server