Skip to main content
Glama
Zabbix MCP Server

Zabbix MCP Server

report_get

Read-only

Retrieve scheduled Zabbix reports by report or dashboard ID and filter by status, schedule, or recipients to audit delivery.

Instructions

Retrieve scheduled reports. Reports are generated from dashboards on a schedule and delivered to users or user groups via email or other media. Filter by reportids for direct lookup or by dashboardids to find all reports generated from specific dashboards.

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of results to return.
filterNoReturn only results whose properties exactly match the given values (a single value or a list of values per key). Example: {"status": 0} or {"status": [0, 1]}. Keys: active_since (6.0+), active_till (6.0+), cycle (6.0+), dashboardid (6.0+), info (6.0+), lastsent (6.0+), message (6.0+), name (6.0+), period (6.0+), reportid (6.0+), start_time (6.0+), state (6.0+), status (6.0+), subject (6.0+), userid (6.0+), weekdays (6.0+). Text properties cannot be filtered; use 'search' for them.
outputNoProperties of the report object to return. Pass 'extend' for all, 'count' for the number of matches only, or a list of property names. Default when omitted: reportid, name, status. Properties: active_since (6.0+), active_till (6.0+), cycle (6.0+), dashboardid (6.0+), description (6.0+), info (6.0+), lastsent (6.0+), message (6.0+), name (6.0+), period (6.0+), reportid (6.0+), start_time (6.0+), state (6.0+), status (6.0+), subject (6.0+), userid (6.0+), weekdays (6.0+).
searchNoReturn results whose string properties contain the given pattern (case-insensitive; '*' is a wildcard when searchWildcardsEnabled is true). Example: {"name": "web"}. Keys: active_since (6.0+), active_till (6.0+), description (6.0+), info (6.0+), message (6.0+), name (6.0+), subject (6.0+).
serverNoTarget Zabbix server. Available: default. Defaults to 'default' if omitted.
raw_jsonNoStrips the security disclaimer preamble from the response so it is pure JSON. Default: false. Requires the bearer token to have 'allow_raw_json' explicitly enabled by an operator in the admin portal - tokens without that policy receive a PolicyError instead. WARNING: setting true bypasses the prompt-injection mitigation marker that wraps untrusted Zabbix data (host names, item descriptions, problem text). LLM clients (Claude, GPT, Cursor, ...) should leave this false; only programmatic non-LLM consumers (Python scripts, n8n workflows that json.loads the result) should set true.
reportidsNoReturn only reports with the given IDs.
sortfieldNoSort by one or more of: reportid, name, status (a list for several; pair with 'sortorder'). No other property is sortable.
sortorderNoSort order: 'ASC' (ascending) or 'DESC' (descending).
countOutputNoReturn the count of matching results instead of the actual data.
searchByAnyNoIf true, return results matching ANY search field (OR). Default is ALL fields (AND).
dashboardidsNoReturn only reports associated with the given dashboard IDs.
extra_paramsNoOther native report.get parameters, merged into the request as-is. Parameters: expired (6.0+). Sub-object selects (value 'extend', 'count' or a list of property names): selectUserGroups (6.0+), selectUsers (6.0+). Any other key is refused here, because Zabbix would silently ignore it. For a parameter you are sure exists on your release but is not listed, use zabbix_raw_api_call.
searchWildcardsEnabledNoIf true, enable * and ? wildcards in search patterns.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed10 schema fields changedv1.42.2
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / properties / extra_params / anyOf
      Previous value: -[
      -  {
      -    "additionalProperties": true,
      -    "type": "object"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "propertyNames": {
      +      "enum": [
      +        "excludeSearch",
      +        "preservekeys",
      +        "startSearch",
      +        "expired",
      +        "selectUserGroups",
      +        "selectUsers"
      +      ]
      +    },
      +    "type": "object"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedInput schema / properties / filter / anyOf
      Previous value: -[
      -  {
      -    "additionalProperties": true,
      -    "type": "object"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "propertyNames": {
      +      "enum": [
      +        "active_since",
      +        "active_till",
      +        "cycle",
      +        "dashboardid",
      +        "info",
      +        "lastsent",
      +        "message",
      +        "name",
      +        "period",
      +        "reportid",
      +        "start_time",
      +        "state",
      +        "status",
      +        "subject",
      +        "userid",
      +        "weekdays"
      +      ]
      +    },
      +    "type": "object"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedInput schema / properties / output / anyOf
      Previous value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "enum": [
      +      "extend",
      +      "count"
      +    ],
      +    "type": "string"
      +  },
      +  {
      +    "items": {
      +      "enum": [
      +        "active_since",
      +        "active_till",
      +        "cycle",
      +        "dashboardid",
      +        "description",
      +        "info",
      +        "lastsent",
      +        "message",
      +        "name",
      +        "period",
      +        "reportid",
      +        "start_time",
      +        "state",
      +        "status",
      +        "subject",
      +        "userid",
      +        "weekdays"
      +      ],
      +      "type": "string"
      +    },
      +    "minItems": 1,
      +    "type": "array"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedInput schema / properties / output / description
      Previous value: -"Properties of the report object to return. Pass 'extend' for all, 'count' for the number of matches only, or a comma-separated list of property names. Default when omitted: reportid, name, status. Properties: active_since (6.0+), active_till (6.0+), cycle (6.0+), dashboardid (6.0+), description (6.0+), info (6.0+), lastsent (6.0+), message (6.0+), name (6.0+), period (6.0+), reportid (6.0+), start_time (6.0+), state (6.0+), status (6.0+), subject (6.0+), userid (6.0+), weekdays (6.0+)."New value: +"Properties of the report object to return. Pass 'extend' for all, 'count' for the number of matches only, or a list of property names. Default when omitted: reportid, name, status. Properties: active_since (6.0+), active_till (6.0+), cycle (6.0+), dashboardid (6.0+), description (6.0+), info (6.0+), lastsent (6.0+), message (6.0+), name (6.0+), period (6.0+), reportid (6.0+), start_time (6.0+), state (6.0+), status (6.0+), subject (6.0+), userid (6.0+), weekdays (6.0+)."
    • changedInput schema / properties / search / anyOf
      Previous value: -[
      -  {
      -    "additionalProperties": true,
      -    "type": "object"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "propertyNames": {
      +      "enum": [
      +        "active_since",
      +        "active_till",
      +        "description",
      +        "info",
      +        "message",
      +        "name",
      +        "subject"
      +      ]
      +    },
      +    "type": "object"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedInput schema / properties / sortfield / anyOf
      Previous value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "enum": [
      +      "reportid",
      +      "name",
      +      "status"
      +    ],
      +    "type": "string"
      +  },
      +  {
      +    "items": {
      +      "enum": [
      +        "reportid",
      +        "name",
      +        "status"
      +      ],
      +      "type": "string"
      +    },
      +    "minItems": 1,
      +    "type": "array"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedInput schema / properties / sortfield / description
      Previous value: -"Sort by one or more of: reportid, name, status (comma-separated for several; pair with 'sortorder'). No other property is sortable."New value: +"Sort by one or more of: reportid, name, status (a list for several; pair with 'sortorder'). No other property is sortable."
    • changedInput schema / properties / sortorder / anyOf
      Previous value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "enum": [
      +      "ASC",
      +      "DESC"
      +    ],
      +    "type": "string"
      +  },
      +  {
      +    "items": {
      +      "enum": [
      +        "ASC",
      +        "DESC"
      +      ],
      +      "type": "string"
      +    },
      +    "minItems": 1,
      +    "type": "array"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedOutput schema / (root)
      Previous value: -{
      -  "properties": {
      -    "result": {
      -      "title": "Result",
      -      "type": "string"
      -    }
      -  },
      -  "required": [
      -    "result"
      -  ],
      -  "title": "report_getOutput",
      -  "type": "object"
      -}New value: +null
  2. First observedv1.41.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered by structured data. The description adds useful domain context that reports are schedule-generated from dashboards and delivered to users/groups, but says nothing about result volume, pagination with 'limit', or how filtering behaves when no filter is given.

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, front-loaded with the verb and resource before background and filtering guidance. The middle sentence about scheduling and delivery is slightly expository but carries real context about what a report row represents; nothing is redundant.

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?

For a 14-parameter, zero-required tool with no output schema, the description covers purpose and lookup strategy but leaves the agent to discover return shape and pagination entirely from the schema. It is adequate given the rich schema but not thorough for a tool of this complexity.

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% and every parameter, including the complex filter/search/output/extra_params objects, is documented in the schema. The description's only semantic addition is the direct-ID lookup versus dashboard-association distinction, which the schema already conveys almost as clearly, so this stays at baseline.

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 a specific verb and resource ('Retrieve scheduled reports') and explains what a report is (dashboard-derived, scheduled, delivered by email or other media), which an agent cannot infer from the name alone. It does not explicitly distinguish itself from the sibling report_generate, which is the main remaining gap.

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?

It gives routing guidance among its own parameters ('filter by reportids for direct lookup or by dashboardids to find all reports generated from specific dashboards'), which is genuinely useful. However, it never states when to use this tool versus report_generate or dashboard_get, and gives no exclusions or prerequisites.

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