Skip to main content
Glama
Zabbix MCP Server

Zabbix MCP Server

by mhajder

Script Get

script_get
Read-onlyIdempotent

Retrieve custom automation scripts from Zabbix to support remediation and configuration tasks on monitored hosts or the server.

Instructions

Get scripts from Zabbix.

Scripts are custom automation routines that can be executed on monitored hosts or the server. They can be triggered manually or by actions to automate remediation or configuration tasks.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "script_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of results to return. Default is 100.
offsetNoNumber of matching records to skip. Use with 'limit' to page through results; check 'has_more' and 'total' in the response.
outputNoextend
searchNoDictionary with search criteria like {'name': 'restart'}.
hostidsNoList of host IDs to get scripts for. An empty list matches none.
groupidsNoList of group IDs to get scripts for hosts in those groups. An empty list matches none.
scriptidsNoList of script IDs to get. Omit to return all scripts; an empty list matches none.
sortfieldNoField to sort by. A deterministic sort is required for paging to be consistent.scriptid
sortorderNoSort direction - 'ASC' or 'DESC'.ASC
count_outputNoIf true, returns only the count of matched objects as an integer.
filter_paramsNoAdditional filter parameters for advanced filtering.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.7.1
    • changedInput schema / properties / groupids / description
      Previous value: -"List of group IDs to get scripts for hosts in those groups."New value: +"List of group IDs to get scripts for hosts in those groups. An empty list matches none."
    • changedInput schema / properties / hostids / description
      Previous value: -"List of host IDs to get scripts for."New value: +"List of host IDs to get scripts for. An empty list matches none."
    • changedInput schema / properties / scriptids / description
      Previous value: -"List of script IDs to get. If empty, returns all scripts."New value: +"List of script IDs to get. Omit to return all scripts; an empty list matches none."
  2. Changed5 schema fields changedv0.6.0
    • changedInput schema / properties / offset / description
      Previous value: -"Number of results to skip (for pagination). Requires sortfield to be set."New value: +"Number of matching records to skip. Use with 'limit' to page through results; check 'has_more' and 'total' in the response."
    • removedInput schema / properties / sortfield / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • changedInput schema / properties / sortfield / default
      Previous value: -nullNew value: +"scriptid"
    • changedInput schema / properties / sortfield / description
      Previous value: -"Field to sort by."New value: +"Field to sort by. A deterministic sort is required for paging to be consistent."
    • addedInput schema / properties / sortfield / type
      Added value: +"string"
  3. First observedv0.5.3

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is fully covered structurally. The description adds useful domain framing about what scripts are used for, but says nothing about permissions, return volume, or paging behavior beyond what annotations and schema already give.

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?

Front-loaded with the core action in one short sentence; the follow-up definition of scripts is relevant domain context. Slightly padded — the second sentence could be trimmed — but nothing is misleading or wasteful.

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?

With 11 parameters, an output schema present, and rich schema descriptions, the definition is functionally sufficient to call the tool. However, for a list tool with search/host/group filtering, the description gives no hint that these filtering capabilities exist, leaving the agent to discover them purely from the schema.

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 91%, so nearly every parameter (limit, offset, search, hostids, groupids, scriptids, sortfield, count_output) is already documented in the schema. The description adds no parameter-level meaning, which is the baseline-3 case when the schema carries the load.

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?

States a clear verb and resource ('Get scripts from Zabbix') and adds a definition of what a script is. An agent can tell this is a read/list operation on scripts, but the description never distinguishes it from the sibling 'script_execute', which is the key ambiguity an agent faces here.

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 on when to use this versus 'script_execute' or any other sibling, and no mention of the filtering/paging behavior that would tell an agent how to narrow a query. Usage is only implied by the tool name.

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