Skip to main content
Glama
Zabbix MCP Server

Zabbix MCP Server

by mhajder

Action Get

action_get
Read-onlyIdempotent

Retrieve Zabbix actions to inspect automated responses to problems and triggers, including notifications and remote commands, with filtering and paging options.

Instructions

Get actions from Zabbix.

Actions define automated responses to problems/triggers. They specify what happens when problems occur - sending notifications, executing remote commands, etc.

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": "action_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': 'notify'}.
hostidsNoList of host IDs to get actions for. An empty list matches none.
groupidsNoList of host group IDs to get actions for. An empty list matches none.
actionidsNoList of action IDs to get. Omit to return all actions; an empty list matches none.
sortfieldNoField to sort by. A deterministic sort is required for paging to be consistent.actionid
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 / actionids / description
      Previous value: -"List of action IDs to get. If empty, returns all actions."New value: +"List of action IDs to get. Omit to return all actions; an empty list matches none."
    • changedInput schema / properties / groupids / description
      Previous value: -"List of host group IDs to get actions for."New value: +"List of host group IDs to get actions for. An empty list matches none."
    • changedInput schema / properties / hostids / description
      Previous value: -"List of host IDs to get actions for."New value: +"List of host IDs to get actions for. 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: +"actionid"
    • 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 covered. The description contributes useful domain semantics about what actions represent, but says nothing about auth requirements, paging behavior, or what the returned objects contain beyond the schema.

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?

Three short sentences with the core operation front-loaded; the second paragraph is domain explanation rather than padding, though it could be trimmed slightly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With a full output schema, rich annotations, and 91% schema coverage, the description only needs to frame the resource, which it does. It is adequate for correct invocation, with only usage routing left implicit.

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 the schema already documents nearly every parameter including limit, offset, search and the id filters. The description adds no parameter guidance, so the baseline 3 applies.

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?

It states a specific verb and resource ('Get actions from Zabbix') and adds a concise definition of what an action is (automated responses to problems/triggers). The resource is unambiguous and no sibling shares it, though there is no explicit differentiation text.

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?

It explains what actions are but not when to call this tool versus alternatives, nor when to filter by hostids/groupids/actionids versus using search. The agent must infer usage entirely from the schema.

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