Skip to main content
Glama
mpeirone

zabbix-mcp-server

item_create

Create new monitoring items in Zabbix by specifying name, key, host ID, type, value type, update interval, units, and description. Returns JSON formatted creation result.

Instructions

Create a new item in Zabbix.

Args:
    name: Item name
    key_: Item key
    hostid: Host ID
    type: Item type (0=Zabbix agent, 2=Zabbix trapper, etc.)
    value_type: Value type (0=float, 1=character, 3=unsigned int, 4=text)
    delay: Update interval
    units: Value units
    description: Item description
    
Returns:
    str: JSON formatted creation result

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
delayNo1m
descriptionNo
hostidYes
key_Yes
nameYes
typeYes
unitsNo
value_typeYes

Implementation Reference

  • The handler function for the 'item_create' tool, registered via @mcp.tool() decorator. It validates read-only mode, gets the Zabbix API client, constructs parameters for item creation, calls client.item.create(), and returns formatted JSON response.
    @mcp.tool()
    def item_create(name: str, key_: str, hostid: str, type: int,
                    value_type: int, delay: str = "1m",
                    units: Optional[str] = None,
                    description: Optional[str] = None) -> str:
        """Create a new item in Zabbix.
        
        Args:
            name: Item name
            key_: Item key
            hostid: Host ID
            type: Item type (0=Zabbix agent, 2=Zabbix trapper, etc.)
            value_type: Value type (0=float, 1=character, 3=unsigned int, 4=text)
            delay: Update interval
            units: Value units
            description: Item description
            
        Returns:
            str: JSON formatted creation result
        """
        validate_read_only()
        
        client = get_zabbix_client()
        params = {
            "name": name,
            "key_": key_,
            "hostid": hostid,
            "type": type,
            "value_type": value_type,
            "delay": delay
        }
        
        if units:
            params["units"] = units
        if description:
            params["description"] = description
        
        result = client.item.create(**params)
        return format_response(result)
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 states it 'creates' which implies a write/mutation operation, but doesn't mention authentication requirements, potential side effects, error conditions, or what the JSON result contains. For a creation tool with zero annotation coverage, 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.

Conciseness4/5

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

The description is well-structured with clear sections (Args, Returns) and efficiently conveys necessary information. Every sentence earns its place, though the opening statement could be slightly more informative about the tool's scope or constraints.

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 complexity of an 8-parameter creation tool with no annotations and no output schema, the description is partially complete. It excels at parameter documentation but lacks behavioral context, usage guidelines, and details about the return value beyond 'JSON formatted creation result'. For a mutation tool, this leaves important gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description provides excellent parameter semantics that fully compensate for the 0% schema description coverage. It clearly explains what each of the 8 parameters represents (e.g., 'type: Item type (0=Zabbix agent, 2=Zabbix trapper, etc.)', 'value_type: Value type (0=float, 1=character, 3=unsigned int, 4=text)'), adding crucial meaning beyond the bare schema field names.

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 'Create' and resource 'new item in Zabbix', making the purpose unambiguous. However, it doesn't explicitly differentiate from sibling tools like 'item_update' or 'item_delete', which would require mentioning it's specifically for initial creation rather than modification or removal.

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 'item_update' or 'item_get'. The description only states what it does without context about prerequisites, appropriate scenarios, or comparisons to sibling tools in the list.

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