Skip to main content
Glama
Zabbix MCP Server

Zabbix MCP Server

by mhajder

Trend Get

trend_get
Read-onlyIdempotent

Retrieve aggregated hourly min/max/average trend data for Zabbix items to enable long-term analysis while using less storage than raw history.

Instructions

Get trend data from Zabbix.

Trends are aggregated (summarized) historical data providing min/max/average values at hour-long intervals. Trends use less storage than raw history while preserving statistical information for long-term analysis.

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": {
      "itemids": "<itemids>"
    },
    "name": "trend_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of results to return. Default is 100.
itemidsYesItem IDs to get trends for.
time_fromNoUnix timestamp to get trends from this time onwards.
time_tillNoUnix timestamp to get trends up to this time.
count_outputNoIf true, returns only the count of matched objects as an integer.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.6.0
    • addedInput schema / properties / itemids / minItems
      Added value: +1
    • removedInput schema / properties / offset
      Removed value: -{
      -  "default": 0,
      -  "description": "Number of results to skip (for pagination). Requires sortfield to be set.",
      -  "minimum": 0,
      -  "type": "integer"
      -}
    • removedInput schema / properties / sortfield
      Removed value: -{
      -  "anyOf": [
      -    {
      -      "type": "string"
      -    },
      -    {
      -      "type": "null"
      -    }
      -  ],
      -  "default": null,
      -  "description": "Field to sort by."
      -}
    • removedInput schema / properties / sortorder
      Removed value: -{
      -  "default": "ASC",
      -  "description": "Sort direction - 'ASC' or 'DESC'.",
      -  "type": "string"
      -}
  2. First observedv0.5.3

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), so the description's real contribution is disclosing that results are aggregated at hour-long intervals with min/max/average stats rather than point samples. That granularity disclosure materially affects how an agent interprets returned values. It omits pagination/limit behavior, but the schema covers that.

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 sentences, front-loaded with the action and followed by the definitional context that justifies the tool's existence. The second sentence earns its place by explaining why trends exist, though it could be trimmed slightly without loss.

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

Completeness5/5

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

Output schema and full parameter documentation are present, annotations cover safety, so the description only needed to explain purpose and data semantics — which it does. An agent can correctly decide to call this and understand the shape of the data (hourly aggregates) without further context.

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% with five well-documented parameters, so the schema already carries the semantics of itemids, time_from, time_till, limit, and count_output. The description adds no parameter-level meaning (e.g., that time_from/time_till filter the aggregation window), which is the correct baseline of 3 given full schema coverage.

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 specific verb+resource ('Get trend data from Zabbix') and then defines what a trend actually is (aggregated min/max/average at hour-long intervals), which effectively separates it from history_get without naming it. It stops short of explicitly naming the sibling alternative, so it is clear but not fully differentiated.

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?

Usage is only implied: the note that trends use less storage than raw history for 'long-term analysis' hints that this tool is for coarse/long-range queries and history_get for raw detail, but no explicit when-to-use or when-not-to-use statement is given. An agent must infer the boundary with history_get from a passing phrase.

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