Skip to main content
Glama
initMAX

Zabbix MCP Server

by initMAX
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

report_generate

Read-only

Generate PDF reports from Zabbix monitoring data for availability, host capacity, network bandwidth, or backup success, returning a resource link instead of the document.

Instructions

Generate a PDF report from Zabbix monitoring data. Supported report types: availability (SLA/uptime), capacity_host (CPU/memory/disk), capacity_network (bandwidth/traffic), backup (daily success/fail matrix).

Returns a link, not the document, so a multi-megabyte PDF never enters the conversation: always a zabbix://reports/<id> MCP resource, and - when the operator configured a public address for this server - a download_url any browser can open. Give the user the download_url when it is there; when it is not, the response says why in download_url_unavailable and the resource link still holds the file. Links expire (an hour by default). Pass as_link: false for the old inline base64 data URI - only practical for small reports.

Two further deliveries exist when the operator enabled them: save_to_file: true writes the PDF into the server's configured report directory, and email_to: "ops@example.com" mails it as an attachment. Both answer with a short receipt (path / recipients / size) and are refused with a clear message when not configured.

Long-running (5-30 s typically). Clients that support the MCP tasks extension may invoke this with task: {ttl: 60000} to get a task handle and poll tasks/get instead of holding a single long HTTP request - useful when fronted by a proxy with short timeouts.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
periodNoReport period: '7d', '30d', '90d' (default: '30d')30d
serverNoTarget Zabbix server. Available: default. Defaults to 'default' if omitted.
as_linkNoDefault true: return a link (an https download_url the user can click, plus the zabbix://reports/<id> MCP resource) instead of the PDF itself, so the document stays out of the conversation context. Set false to force the inline base64 data URI, which is only practical for small reports.
companyNoCompany name for report header (overrides config)
email_toNoComma-separated recipients to email the PDF to as an attachment instead of returning it inline. Requires [reporting.email] and each address must match the operator's allowed_recipients.
hostgroupidYesHost group ID to include in the report
report_typeYesReport type: 'availability', 'capacity_host', 'capacity_network', 'backup'
save_to_fileNoWrite the PDF to the server's configured report directory instead of returning it inline. Requires [reporting].output_dir. Returns the path.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.41.0

TDQS

A4.8/5.0
Behavior5/5

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

Goes well past the annotations: discloses that links expire (~1h), that the response contains download_url_unavailable with a reason, that file/email modes return a short receipt or a clear refusal, and that runs take 5-30s. This is exactly the operational context an agent needs and cannot get from readOnlyHint/openWorldHint.

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 purpose then delivery mechanics, which is the right order; each paragraph covers a distinct concern. It is long, and the 'link not the document' point is restated in both paragraph one and the as_link schema, so a little tightening is possible.

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?

For an 8-parameter, long-running, no-output-schema tool this covers the return contract (resource link, download_url, receipt shapes, expiry), failure modes, and async invocation. Nothing material is left for the agent to guess.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3; the description earns an extra point by adding prerequisite semantics the schema only gestures at (email_to requires allowed_recipients matching, save_to_file requires output_dir, as_link:false degrades to a base64 data URI). It stops short of documenting period/serve/company beyond the schema text.

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

Purpose5/5

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

States a specific verb+resource ('Generate a PDF report from Zabbix monitoring data') and enumerates the four supported report types, which cleanly separates it from the passive retrieval sibling report_get. An agent can tell what it produces without opening the schema.

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

Usage Guidelines5/5

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

Explicitly routes the agent: give the user download_url when present, use as_link:false only for small reports, enable save_to_file/email_to only when the operator configured them, and use task:{ttl} when behind a short-timeout proxy. When-not conditions and alternatives are stated, not implied.

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

Deploy Server

Other Tools