mcp-zabbix

by daedalus

Overview Schema Source Related Servers Discussions Admin

Python

Remote

zabbix_trend_get

Retrieve historical monitoring trend data from Zabbix for time series analysis and reporting.

Instructions

Zabbix API trend.get method

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": "zabbix_trend_get"
  }
}

Input Schema

Name	Required	Description	Default
`params`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Apr 18, 2026

TDQS

D1.1/5.0

Behavior1/5

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

No annotations exist, so the description must disclose behavioral traits. It fails to mention that this is a read operation, the nature of the trend data, or any side effects. It adds no behavioral context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is short but overly vague; it prioritizes brevity over information. Every word should add value, and here 'Zabbix API' and 'method' are redundant with the tool name.

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

Completeness1/5

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

For a moderately complex Zabbix API call with an output schema, the description must explain inputs and outputs. It is completely inadequate, providing zero context for the agent to select or use the tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has one free-form params object with 0% description coverage. The description provides no explanation of valid keys (e.g., itemids, time_from) or their purpose, leaving the agent with no guidance.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description is a tautology: 'Zabbix API trend.get method' simply restates the tool name without specifying what the method does (e.g., retrieve historical trend data).

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

Usage Guidelines1/5

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

No guidance is provided on when to use this tool versus siblings like zabbix_trend_create or zabbix_trend_get alternatives. The description lacks any usage context.

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

Deploy Server