Skip to main content
Glama
Zabbix MCP Server

Zabbix MCP Server

by mhajder

Script Execute

script_execute
Destructive

Execute a custom script on a specified Zabbix host to run remediation tasks, apply configuration changes, or perform remote diagnostics.

Instructions

Execute a script on a host in Zabbix.

Runs a custom script on a specified host. Used for executing remediation tasks, configuration changes, or diagnostic commands remotely.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "scriptid": "<scriptid>",
      "hostid": "<hostid>"
    },
    "name": "script_execute"
  }
}

Input Schema

NameRequiredDescriptionDefault
hostidYesHost ID to execute the script on.
scriptidYesScript ID to execute.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.3

TDQS

B3.4/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare destructiveHint=true, readOnlyHint=false and idempotentHint=false, so the risk profile is known. The description adds useful context that this runs arbitrary commands remotely for remediation or configuration changes, which is consistent with the annotations, but it does not warn about irreversibility, permission requirements, or that results depend entirely on the script's contents. It adds some value over the annotations without being rich behavioral detail.

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?

Two short sentences with the core action front-loaded. The second sentence earns its place by narrowing the action domain, though it partially restates the first and could be merged.

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?

An output schema exists, so return values need not be explained, and parameters are fully covered by the schema. However, for a destructive remote-execution tool the description omits key operational caveats — prerequisite of a pre-existing script, execution target type (agent/proxy/server), permission requirements, and whether the call is asynchronous. These are material gaps for correct invocation.

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?

Schema description coverage is 100% for both required parameters (hostid and scriptid), so the schema fully documents them. The description adds no format, source, or discovery hints (e.g., where to obtain a valid scriptid) beyond what the schema provides. Baseline 3 applies when the schema carries the parameter burden.

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 first sentence gives a specific verb and resource ("Execute a script on a host in Zabbix") that clearly separates it from script_get, the only script-related sibling. The second sentence reinforces scope by naming the kinds of actions performed. It stops short of explicitly contrasting itself with siblings, so it lands at 4 rather than 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

"Used for executing remediation tasks, configuration changes, or diagnostic commands remotely" implies the usage context, but there is no explicit when-to-use versus when-not, no mention that the script must already be defined in Zabbix, and no guidance on prerequisites such as permissions or target host type. The agent must infer these from context.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.