IAC Memory MCP Server

Overview Schema Source Related Servers Discussions Admin

list_terraform_providers

Retrieve cached Terraform providers with metadata to manage Infrastructure-as-Code resources. Filter results using name patterns for targeted access.

Instructions

List all cached Terraform providers with basic metadata

Input Schema

TableJSON Schema

Name	Required	Description	Default
`filter_criteria`	No	Optional filtering criteria

Implementation Reference

src/iac_memory_mcp_server/db/tools.py:48-64 (schema)

Schema definition for the list_terraform_providers tool, specifying input parameters including optional filter_criteria with name_pattern for provider names.

"list_terraform_providers": {
    "type": "object",
    "description": "List all cached Terraform providers with basic metadata",
    "required": [],
    "properties": {
        "filter_criteria": {
            "type": "object",
            "description": "Optional filtering criteria",
            "properties": {
                "name_pattern": {
                    "type": "string",
                    "description": "Regex pattern to filter provider names",
                }
            },
        }
    },
},

src/iac_memory_mcp_server/tools/__init__.py:46-55 (registration)

Registration of the list_tools handler which includes 'list_terraform_providers' via TOOL_SCHEMAS from db/tools.py.

@server.call_tool()
async def call_tool(
    name: str, arguments: Dict[str, Any], ctx: RequestContext | None = None
):
    return await handle_call_tool(name, arguments, ctx)

@server.list_tools()
async def list_tools(ctx: RequestContext = None):
    return await handle_list_tools(ctx)

Schema Changelog

Changes observed during successful MCP inspections.

First observedAug 18, 2025

TDQS

B3.1/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions 'cached' providers and 'basic metadata', but fails to specify what 'cached' means (e.g., local vs. remote), the format of the list (e.g., paginated, sorted), or any limitations (e.g., rate limits, authentication needs). This leaves significant gaps for a tool that likely interacts with a system state.

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 a single, efficient sentence that front-loads the core action ('List all cached Terraform providers') and adds necessary context ('with basic metadata') without redundancy. Every word earns its place, making it highly concise and well-structured.

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 no annotations and no output schema, the description is incomplete for a tool that likely returns a list of providers. It specifies the resource and scope but omits details on return format (e.g., structure of 'basic metadata'), error handling, or system dependencies. This is adequate as a minimum but has clear gaps in contextual information.

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 description coverage is 100%, so the schema fully documents the optional 'filter_criteria' parameter and its 'name_pattern' sub-property. The description does not add any parameter details beyond what the schema provides, such as examples of regex patterns or filtering behavior, meeting the baseline for high schema coverage.

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 verb ('List') and resource ('all cached Terraform providers'), specifying the scope ('all cached') and output ('with basic metadata'). It distinguishes from siblings like 'get_terraform_provider_info' by indicating a list operation rather than detailed info retrieval, though it doesn't explicitly contrast with 'list_provider_resources'.

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 is provided on when to use this tool versus alternatives like 'get_terraform_provider_info' for detailed metadata or 'list_provider_resources' for related resources. The description implies usage for listing providers but lacks explicit context, prerequisites, or exclusions.

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