Skip to main content
Glama
AgentWong

IAC Memory MCP Server

by AgentWong

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
NameRequiredDescriptionDefault
filter_criteriaNoOptional filtering criteria

Implementation Reference

  • 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",
                    }
                },
            }
        },
    },
  • 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)
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states it's a list operation, implying it's read-only and non-destructive, but doesn't specify aspects like pagination, rate limits, authentication needs, or what 'basic metadata' includes. For a tool with no annotations, this leaves significant behavioral gaps.

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 directly states the tool's purpose without unnecessary words. It's front-loaded with the core action ('List all cached Terraform providers') and includes essential context ('with basic metadata'), 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 the tool's low complexity (one optional parameter, no output schema, no annotations), the description is minimally adequate. It covers the basic purpose but lacks details on usage guidelines, behavioral traits, and output specifics. For a list tool with no annotations or output schema, it should ideally clarify what 'basic metadata' entails or how results are returned to be more complete.

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 has 100% description coverage, documenting the optional 'filter_criteria' parameter with its 'name_pattern' property. The description doesn't add any parameter-specific details beyond what's in the schema, such as examples of regex patterns or how filtering works. With high schema coverage, the baseline score of 3 is appropriate as the schema handles the parameter documentation adequately.

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 the resource 'all cached Terraform providers with basic metadata', making the purpose evident. However, it doesn't explicitly differentiate from sibling tools like 'list_ansible_collections' or 'list_provider_resources', which would require mentioning Terraform-specific context to distinguish them.

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?

The description provides no guidance on when to use this tool versus alternatives. For example, it doesn't mention when to choose 'list_terraform_providers' over 'get_terraform_provider_info' (which might fetch detailed info for a single provider) or 'list_provider_resources' (which might list resources within providers). This lack of context leaves the agent without clear usage direction.

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/AgentWong/iac-memory-mcp-server'

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