Skip to main content
Glama
Zabbix MCP Server

Zabbix MCP Server

map_get

Read-only

Retrieve Zabbix network maps (sysmaps) to view infrastructure topology with hosts, groups, triggers, elements, and status links. Filter, sort, and select map structure details.

Instructions

Retrieve network maps (sysmaps). Maps provide a visual topology view of your infrastructure, showing hosts, host groups, triggers, and the connections between them. Maps can contain elements (hosts, groups, images, triggers) and links (connections with status indicators). Use 'selectElements' and 'selectLinks' in the filter to include map structure details.

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: background_scale (7.4+), backgroundid, expand_macros, expandproblem, grid_align, grid_show, grid_size, height, highlight, iconmapid, label_format, label_location, label_string_host, label_string_hostgroup, label_string_image, label_string_map, label_string_trigger, label_type, label_type_host, label_type_hostgroup, label_type_image, label_type_map, label_type_trigger, markelements, name, private, severity_min, show_element_label (7.4+), show_link_label (7.4+), show_suppressed, show_unack, sysmapid, userid, width. Text properties cannot be filtered; use 'search' for them.
outputNoProperties of the map object to return. Pass 'extend' for all, 'count' for the number of matches only, or a list of property names. Default when omitted: sysmapid, name. Properties: background_scale (7.4+), backgroundid, expand_macros, expandproblem, grid_align, grid_show, grid_size, height, highlight, iconmapid, label_format, label_location, label_string_host, label_string_hostgroup, label_string_image, label_string_map, label_string_trigger, label_type, label_type_host, label_type_hostgroup, label_type_image, label_type_map, label_type_trigger, markelements, name, private, severity_min, show_element_label (7.4+), show_link_label (7.4+), show_suppressed, show_unack, sysmapid, userid, width.
searchNoReturn results whose string properties contain the given pattern (case-insensitive; '*' is a wildcard when searchWildcardsEnabled is true). Example: {"name": "web"}. Keys: label_string_host, label_string_hostgroup, label_string_image, label_string_map, label_string_trigger, name.
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.
sortfieldNoSort by one or more of: name, width, height (a list for several; pair with 'sortorder'). No other property is sortable.
sortorderNoSort order: 'ASC' (ascending) or 'DESC' (descending).
sysmapidsNoReturn only maps with the given IDs.
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).
extra_paramsNoOther native map.get parameters, merged into the request as-is. Parameters: expandUrls, userids. Switches (true turns one on, false is the same as leaving it out): expandUrls. Sub-object selects (value 'extend', 'count' or a list of property names): selectIconMap, selectLines, selectLinks, selectSelements, selectShapes, selectUrls, selectUserGroups, selectUsers. 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. Changed11 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": [
      +        "editable",
      +        "excludeSearch",
      +        "preservekeys",
      +        "startSearch",
      +        "expandUrls",
      +        "userids",
      +        "selectIconMap",
      +        "selectLines",
      +        "selectLinks",
      +        "selectSelements",
      +        "selectShapes",
      +        "selectUrls",
      +        "selectUserGroups",
      +        "selectUsers"
      +      ]
      +    },
      +    "type": "object"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedInput schema / properties / extra_params / description
      Previous value: -"Other native map.get parameters, merged into the request as-is. Parameters: expandUrls, userids. Sub-object selects (value 'extend', 'count' or a list of property names): selectIconMap, selectLines, selectLinks, selectSelements, selectShapes, selectUrls, selectUserGroups, selectUsers. 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."New value: +"Other native map.get parameters, merged into the request as-is. Parameters: expandUrls, userids. Switches (true turns one on, false is the same as leaving it out): expandUrls. Sub-object selects (value 'extend', 'count' or a list of property names): selectIconMap, selectLines, selectLinks, selectSelements, selectShapes, selectUrls, selectUserGroups, selectUsers. 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."
    • changedInput schema / properties / filter / anyOf
      Previous value: -[
      -  {
      -    "additionalProperties": true,
      -    "type": "object"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "propertyNames": {
      +      "enum": [
      +        "background_scale",
      +        "backgroundid",
      +        "expand_macros",
      +        "expandproblem",
      +        "grid_align",
      +        "grid_show",
      +        "grid_size",
      +        "height",
      +        "highlight",
      +        "iconmapid",
      +        "label_format",
      +        "label_location",
      +        "label_string_host",
      +        "label_string_hostgroup",
      +        "label_string_image",
      +        "label_string_map",
      +        "label_string_trigger",
      +        "label_type",
      +        "label_type_host",
      +        "label_type_hostgroup",
      +        "label_type_image",
      +        "label_type_map",
      +        "label_type_trigger",
      +        "markelements",
      +        "name",
      +        "private",
      +        "severity_min",
      +        "show_element_label",
      +        "show_link_label",
      +        "show_suppressed",
      +        "show_unack",
      +        "sysmapid",
      +        "userid",
      +        "width"
      +      ]
      +    },
      +    "type": "object"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedInput schema / properties / output / anyOf
      Previous value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "enum": [
      +      "extend",
      +      "count"
      +    ],
      +    "type": "string"
      +  },
      +  {
      +    "items": {
      +      "enum": [
      +        "background_scale",
      +        "backgroundid",
      +        "expand_macros",
      +        "expandproblem",
      +        "grid_align",
      +        "grid_show",
      +        "grid_size",
      +        "height",
      +        "highlight",
      +        "iconmapid",
      +        "label_format",
      +        "label_location",
      +        "label_string_host",
      +        "label_string_hostgroup",
      +        "label_string_image",
      +        "label_string_map",
      +        "label_string_trigger",
      +        "label_type",
      +        "label_type_host",
      +        "label_type_hostgroup",
      +        "label_type_image",
      +        "label_type_map",
      +        "label_type_trigger",
      +        "markelements",
      +        "name",
      +        "private",
      +        "severity_min",
      +        "show_element_label",
      +        "show_link_label",
      +        "show_suppressed",
      +        "show_unack",
      +        "sysmapid",
      +        "userid",
      +        "width"
      +      ],
      +      "type": "string"
      +    },
      +    "minItems": 1,
      +    "type": "array"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedInput schema / properties / output / description
      Previous value: -"Properties of the map 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: sysmapid, name. Properties: background_scale (7.4+), backgroundid, expand_macros, expandproblem, grid_align, grid_show, grid_size, height, highlight, iconmapid, label_format, label_location, label_string_host, label_string_hostgroup, label_string_image, label_string_map, label_string_trigger, label_type, label_type_host, label_type_hostgroup, label_type_image, label_type_map, label_type_trigger, markelements, name, private, severity_min, show_element_label (7.4+), show_link_label (7.4+), show_suppressed, show_unack, sysmapid, userid, width."New value: +"Properties of the map object to return. Pass 'extend' for all, 'count' for the number of matches only, or a list of property names. Default when omitted: sysmapid, name. Properties: background_scale (7.4+), backgroundid, expand_macros, expandproblem, grid_align, grid_show, grid_size, height, highlight, iconmapid, label_format, label_location, label_string_host, label_string_hostgroup, label_string_image, label_string_map, label_string_trigger, label_type, label_type_host, label_type_hostgroup, label_type_image, label_type_map, label_type_trigger, markelements, name, private, severity_min, show_element_label (7.4+), show_link_label (7.4+), show_suppressed, show_unack, sysmapid, userid, width."
    • changedInput schema / properties / search / anyOf
      Previous value: -[
      -  {
      -    "additionalProperties": true,
      -    "type": "object"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "propertyNames": {
      +      "enum": [
      +        "label_string_host",
      +        "label_string_hostgroup",
      +        "label_string_image",
      +        "label_string_map",
      +        "label_string_trigger",
      +        "name"
      +      ]
      +    },
      +    "type": "object"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedInput schema / properties / sortfield / anyOf
      Previous value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "enum": [
      +      "name",
      +      "width",
      +      "height"
      +    ],
      +    "type": "string"
      +  },
      +  {
      +    "items": {
      +      "enum": [
      +        "name",
      +        "width",
      +        "height"
      +      ],
      +      "type": "string"
      +    },
      +    "minItems": 1,
      +    "type": "array"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedInput schema / properties / sortfield / description
      Previous value: -"Sort by one or more of: name, width, height (comma-separated for several; pair with 'sortorder'). No other property is sortable."New value: +"Sort by one or more of: name, width, height (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": "map_getOutput",
      -  "type": "object"
      -}New value: +null
  2. First observedv1.41.0

TDQS

B3/5.0
Behavior3/5

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

Annotations already establish readOnlyHint=true and openWorldHint=false, so the safety profile is clear. The description adds domain context about map elements and links, but it does not disclose return format, pagination behavior, or other operational details beyond the annotations.

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?

The description is three sentences and front-loads the purpose. The middle sentence adds useful domain context, though it could be trimmed slightly. Overall it is clear and not padded.

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 13-parameter read-only retrieval tool with no output schema, the description covers purpose and map structure at a high level. It omits return-value expectations, default output behavior, and pagination context, and its parameter placement hint is inaccurate.

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

Parameters2/5

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

Schema description coverage is 100%, so the schema already documents all parameters thoroughly. The description's only parameter hint says to use 'selectElements' and 'selectLinks' in the filter, but the schema places these under extra_params rather than filter, which is misleading.

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 network maps (sysmaps).' It explains what maps are and what they contain, making the tool's purpose clear. However, it does not explicitly distinguish this tool from sibling retrieval tools such as dashboard_get or templatedashboard_get.

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

Usage Guidelines2/5

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

The description gives no guidance on when to choose map_get over dashboard_get or other topology-related siblings. The only usage-like sentence concerns selectElements and selectLinks, which is parameter guidance rather than tool-selection guidance.

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