Skip to main content
Glama
leroylim

Zabbix MCP Server

by leroylim

zabbix_get_maps

Retrieve network maps from Zabbix, using filters and custom output fields to get only the map data you need.

Instructions

Get network maps from Zabbix with filtering and output options

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoLimit the number of records returned
filterNoReturn only maps that match the given filter
outputNoObject properties to be returned
searchNoReturn only maps that match the given wildcard search
useridsNoReturn only maps that belong to the given users
sortfieldNoSort the result by the given properties
sortorderNoSort orderASC
sysmapidsNoReturn only maps with the given IDs
selectUrlsNoReturn map URLs
selectLinesNoReturn map lines
selectLinksNoReturn map links
selectUsersNoReturn users that have access to the map
selectShapesNoReturn map shapes
selectIconMapNoReturn icon map used by the map
selectSelementsNoReturn map elements
selectUserGroupsNoReturn user groups that have access to the map
Behavior2/5

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

No annotations are provided, so the description carries full responsibility for disclosing behavior. It only states that it retrieves maps and mentions filtering/output; it does not disclose return format, authentication requirements, pagination, or that it is non-destructive. The read-only nature is implied by 'Get' but not confirmed.

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

Conciseness5/5

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

One sentence with no waste; it is front-loaded and appropriately sized for a simple retrieval operation.

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?

Given the tool's complexity (16 params) and lack of output schema/annotations, the description is minimal but sufficient to identify the tool's purpose. However, it lacks details on return structure, usage context, or behavior expectations, leaving gaps for an agent without additional knowledge.

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 coverage is 100%, so the baseline is 3. The description adds no specific parameter information beyond vague 'filtering and output options', but the schema already thoroughly documents all 16 parameters, so the description does not need to compensate.

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 clearly states the action ('Get') and resource ('network maps from Zabbix'), making it distinct from sibling create/update/delete map tools. The addition of 'filtering and output options' hints at functionality but is generic and somewhat redundant given 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 Guidelines3/5

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

The description does not explicitly state when to use this tool vs. alternatives. The verb 'Get' implies it is for retrieval, and sibling names indicate other operations, but no explicit guidance is given about prerequisites or excluded use cases.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/leroylim/zabbix-mcp-server-nodejs'

If you have feedback or need assistance with the MCP directory API, please join our Discord server