Skip to main content
Glama
AgentWong

IAC Memory MCP Server

by AgentWong

get_provider_version_history

Retrieve version history for Terraform providers to track changes and ensure compatibility in infrastructure-as-code projects.

Instructions

Retrieve version history for a specific Terraform provider

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
provider_nameYesName of the Terraform provider

Implementation Reference

  • The handler function that executes the core logic of retrieving Terraform provider version history from the database.
    def get_provider_version_history(db: DatabaseManager, provider_name: str) -> List[Dict]:
        """Get version history for a specific Terraform provider.
    
        Args:
            db: Database manager instance
            provider_name: Name of the provider
    
        Returns:
            List of version entries with timestamps and URLs
        """
        logger.info(
            "Getting provider version history",
            extra={
                "provider_name": provider_name,
                "operation": "get_provider_version_history",
            },
        )
    
        try:
            with db.get_connection() as conn:
                versions = conn.execute(
                    """
                    SELECT version, source_url, doc_url, created_at, updated_at
                    FROM terraform_providers
                    WHERE name = ?
                    ORDER BY created_at DESC
                    """,
                    (provider_name,),
                ).fetchall()
    
                # Add debug logging
                logger.debug(f"Found {len(versions)} versions for provider {provider_name}")
                return [dict(v) for v in versions]
    
        except sqlite3.Error as e:
            error_msg = f"Failed to get provider version history: {str(e)}"
            logger.error(error_msg)
            raise DatabaseError(error_msg)
  • The input schema definition for the get_provider_version_history tool, used for validation and registration.
    "get_provider_version_history": {
        "type": "object",
        "description": "Retrieve version history for a specific Terraform provider",
        "required": ["provider_name"],
        "properties": {
            "provider_name": {
                "type": "string",
                "description": "Name of the Terraform provider",
            }
        },
    },
  • The MCP server registration of tool call and list handlers, which use the TOOL_SCHEMAS including get_provider_version_history schema.
    @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 the action ('Retrieve') but does not describe traits like read-only vs. destructive nature, authentication needs, rate limits, or return format. This is inadequate for a tool with no annotation coverage.

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 is appropriately sized and front-loaded, with no wasted information.

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

Completeness2/5

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

Given the tool has no annotations and no output schema, the description is incomplete. It does not explain what the version history includes (e.g., list of versions, dates, changes) or behavioral aspects, leaving significant gaps for an agent to understand and use the tool effectively.

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 single parameter 'provider_name' as 'Name of the Terraform provider'. The description adds no additional meaning beyond this, such as format examples or constraints, so it meets the baseline for high schema coverage without compensating value.

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 ('Retrieve') and resource ('version history for a specific Terraform provider'), making the purpose unambiguous. However, it does not differentiate from sibling tools like 'get_terraform_provider_info' or 'get_collection_version_history', which might retrieve related but different information.

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, such as 'get_terraform_provider_info' (which might give current info) or 'get_collection_version_history' (for Ansible collections). It lacks explicit context, prerequisites, or exclusions, leaving usage unclear.

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