Skip to main content
Glama
leroylim

Zabbix MCP Server

by leroylim

zabbix_update_script

Update an existing script in Zabbix by providing its ID and modifying properties like name, command, type, or execution options.

Instructions

Update an existing script in Zabbix

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoName of the script
typeNoType of script (0 - script, 1 - IPMI, 2 - SSH, 3 - Telnet, 4 - global script, 5 - URL)
scopeNoScript scope (1 - action operation, 2 - manual host action, 4 - manual event action)
commandNoCommand to execute (for script type) or URL (for URL type)
groupidNoHost group ID that the script can be run on (0 for all groups)
scriptidYesID of the script to update
usrgrpidNoUser group ID that can execute the script (0 for all groups)
execute_onNoWhere to execute the script (0 - Zabbix agent, 1 - Zabbix server, 2 - Zabbix server (proxy))
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, and the description only says 'Update an existing script in Zabbix.' It does not disclose behavioral traits such as whether it performs a partial or full update, requires authentication, or has side effects.

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

Conciseness2/5

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

The description is only one sentence, but it merely restates the tool name without adding useful information. It is under-specified rather than effectively concise.

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?

For an update operation with 11 parameters and no output schema, this description is too terse. It does not explain return values, error conditions, or any operational context beyond the basic action.

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?

All 11 parameters have descriptions in the schema (100% coverage), so the description does not need to add parameter semantics. The baseline is 3 because the schema is sufficient.

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 states the tool updates an existing script in Zabbix, providing a clear verb and resource. It doesn't explicitly differentiate from sibling update/create/delete/execute tools, but the name and 'existing' imply an update operation.

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 creating, deleting, or getting scripts. No prerequisites or context are mentioned.

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