Skip to main content
Glama
mpeirone

zabbix-mcp-server

template_get

Retrieve Zabbix templates using specific filters like template IDs, host group IDs, or host IDs. Returns a JSON-formatted list for easy integration and analysis.

Instructions

Get templates from Zabbix with optional filtering.

Args:
    templateids: List of template IDs to retrieve
    groupids: List of host group IDs to filter by
    hostids: List of host IDs to filter by
    output: Output format
    search: Search criteria
    filter: Filter criteria
    
Returns:
    str: JSON formatted list of templates

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
filterNo
groupidsNo
hostidsNo
outputNoextend
searchNo
templateidsNo

Implementation Reference

  • The handler function decorated with @mcp.tool() that implements the template_get MCP tool. It retrieves templates from the Zabbix API using client.template.get with optional filters and returns formatted JSON.
    def template_get(templateids: Optional[List[str]] = None,
                     groupids: Optional[List[str]] = None,
                     hostids: Optional[List[str]] = None,
                     output: Union[str, List[str]] = "extend",
                     search: Optional[Dict[str, str]] = None,
                     filter: Optional[Dict[str, Any]] = None) -> str:
        """Get templates from Zabbix with optional filtering.
        
        Args:
            templateids: List of template IDs to retrieve
            groupids: List of host group IDs to filter by
            hostids: List of host IDs to filter by
            output: Output format (extend or list of specific fields)
            search: Search criteria
            filter: Filter criteria
            
        Returns:
            str: JSON formatted list of templates
        """
        client = get_zabbix_client()
        params = {"output": output}
        
        if templateids:
            params["templateids"] = templateids
        if groupids:
            params["groupids"] = groupids
        if hostids:
            params["hostids"] = hostids
        if search:
            params["search"] = search
        if filter:
            params["filter"] = filter
        
        result = client.template.get(**params)
        return format_response(result)
  • The @mcp.tool() decorator registers the template_get function as an MCP tool.
    def template_get(templateids: Optional[List[str]] = None,
  • Helper function used by template_get to format the API response as indented JSON.
    def format_response(data: Any) -> str:
        """Format response data as JSON string.
        
        Args:
            data: Data to format
            
        Returns:
            str: JSON formatted string
        """
        return json.dumps(data, indent=2, default=str)
  • Helper function used by template_get to obtain the authenticated Zabbix API client.
    def get_zabbix_client() -> ZabbixAPI:
        """Get or create Zabbix API client with proper authentication.
        
        Returns:
            ZabbixAPI: Authenticated Zabbix API client
            
        Raises:
            ValueError: If required environment variables are missing
            Exception: If authentication fails
        """
        global zabbix_api
        
        if zabbix_api is None:
            url = os.getenv("ZABBIX_URL")
            if not url:
                raise ValueError("ZABBIX_URL environment variable is required")
            
            logger.info(f"Initializing Zabbix API client for {url}")
            
            # Configure SSL verification
            verify_ssl = os.getenv("VERIFY_SSL", "true").lower() in ("true", "1", "yes")
            logger.info(f"SSL certificate verification: {'enabled' if verify_ssl else 'disabled'}")
            
            # Initialize client
            zabbix_api = ZabbixAPI(url=url, validate_certs=verify_ssl)
    
            # Authenticate using token or username/password
            token = os.getenv("ZABBIX_TOKEN")
            if token:
                logger.info("Authenticating with API token")
                zabbix_api.login(token=token)
            else:
                user = os.getenv("ZABBIX_USER")
                password = os.getenv("ZABBIX_PASSWORD")
                if not user or not password:
                    raise ValueError("Either ZABBIX_TOKEN or ZABBIX_USER/ZABBIX_PASSWORD must be set")
                logger.info(f"Authenticating with username: {user}")
                zabbix_api.login(user=user, password=password)
            
            logger.info("Successfully authenticated with Zabbix API")
        
        return zabbix_api
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 tool retrieves templates with filtering and returns JSON, but lacks details on permissions, rate limits, pagination, error handling, or side effects. For a read operation with 6 parameters and no annotation coverage, this is insufficient transparency.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured with a clear purpose statement followed by Args and Returns sections. It's appropriately sized with no redundant information. However, the parameter list could be more integrated into the flow rather than a bullet-like format, slightly affecting readability.

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 6 parameters, no annotations, and no output schema, the description is moderately complete. It covers the basic purpose and parameters but lacks behavioral context, usage guidelines, and detailed return format explanation. It's adequate as a minimum viable description but has clear gaps for effective tool selection.

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?

The description lists all 6 parameters with brief labels, adding meaning beyond the schema which has 0% description coverage. It clarifies that templateids, groupids, and hostids are for filtering, and output is for format, though it doesn't explain values like 'extend' or details for search/filter. With low schema coverage, this compensates well but not fully.

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 tool's purpose: 'Get templates from Zabbix with optional filtering.' It specifies the verb ('Get'), resource ('templates from Zabbix'), and scope ('with optional filtering'). However, it doesn't explicitly differentiate from sibling tools like template_create or template_delete, which would require a 5.

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. It doesn't mention sibling tools like template_create, template_update, or template_delete for comparison, nor does it specify prerequisites or contexts for usage. The only implied usage is retrieving templates, but no explicit guidelines are given.

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

Related 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/mpeirone/zabbix-mcp-server'

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