Skip to main content
Glama
AgentWong
by AgentWong

get_provider_version_history

Retrieve version history for Terraform providers to track changes and ensure compatibility in Infrastructure-as-Code management.

Instructions

Retrieve version history for a specific Terraform provider

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
provider_nameYesName of the Terraform provider

Implementation Reference

  • Core database function that executes the tool logic by querying the terraform_providers table for version history of a specific provider and returns a list of version dictionaries.
    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)
  • Input schema definition for the get_provider_version_history tool, specifying the required provider_name parameter.
    "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",
            }
        },
    },
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 specify whether this is a read-only operation, if it requires authentication, what the return format is (e.g., list of versions with timestamps), or any rate limits. This leaves significant gaps in understanding the tool's behavior.

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 any unnecessary words. It is front-loaded and wastes no space, making it easy to understand at a glance.

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?

For a tool with one parameter and no output schema, the description is minimally adequate but lacks depth. It does not explain what the version history includes (e.g., version numbers, release dates, changelogs) or how the data is structured, which could be important for an agent to interpret results correctly. Given the simplicity, it meets basic needs but could be more informative.

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, with the parameter 'provider_name' clearly documented. The description does not add any extra meaning beyond what the schema provides, such as examples or constraints on the provider name format. Given the high schema coverage, a baseline score of 3 is appropriate.

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 the resource 'version history for a specific Terraform provider', making the purpose unambiguous. However, it does not explicitly differentiate from sibling tools like 'get_terraform_provider_info' or 'get_collection_version_history', which might retrieve different aspects of provider data.

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' or 'get_collection_version_history'. It lacks context about prerequisites, exclusions, or specific scenarios where this tool is preferred over others, leaving usage decisions 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-project'

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