Skip to main content
Glama
leroylim

Zabbix MCP Server

by leroylim

zabbix_create_script

Create a new script in Zabbix for automated actions, manual host operations, or event handling. Define command, type, scope, and execution options to extend monitoring workflows.

Instructions

Create a new script in Zabbix

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesName of the script
portNoPort for SSH/Telnet scripts
typeYesType of script (0 - script, 1 - IPMI, 2 - SSH, 3 - Telnet, 4 - global script, 5 - URL)
scopeYesScript scope (1 - action operation, 2 - manual host action, 4 - manual event action)
commandYesCommand to execute (for script type) or URL (for URL type)
groupidNoHost group ID that the script can be run on (0 for all groups)
authtypeNoAuthentication type for SSH scripts (0 - password, 1 - public key)
passwordNoPassword for SSH/Telnet scripts
usernameNoUsername for SSH/Telnet scripts
usrgrpidNoUser group ID that can execute the script (0 for all groups)
publickeyNoPublic key file name for SSH scripts
execute_onNoWhere to execute the script (0 - Zabbix agent, 1 - Zabbix server, 2 - Zabbix server (proxy))
parametersNoScript parameters for webhook scripts
privatekeyNoPrivate key file name for SSH scripts
descriptionNoDescription of the script
host_accessNoHost permissions needed (2 - read, 3 - write)
confirmationNoConfirmation text to display before executing the script
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 disclosing behavioral traits. However, it only says 'Create a new script' without explaining side effects, required permissions, error conditions, or return values. This adds no transparency beyond what the tool name already implies.

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 extremely concise and well-structured as a single, clear sentence. It front-loads the essential verb and object without redundancy, though it under-specifies details that might be expected in a more complete description.

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 complexity (17 parameters, 4 required, no output schema), the description is severely incomplete. It does not explain return values, required fields, or the overall behavior of script creation, relying entirely on the schema for parameter details and failing to contextualize when and why this tool is used.

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% coverage with descriptions for all 17 parameters, including types, ranges, and meanings. The tool description itself adds no parameter-specific information, so the baseline score of 3 applies as the schema fully documents the parameters.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb (Create), the resource (a new script), and the context (in Zabbix). This distinguishes it from sibling tools like zabbix_update_script, zabbix_delete_scripts, and zabbix_execute_script, which perform different operations on scripts.

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, prerequisites, or context. It does not mention that this is for creating a new script as opposed to updating or executing an existing one, so the agent receives no usage direction beyond the general operation name.

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/leroylim/zabbix-mcp-server-nodejs'

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