Zabbix MCP Server

Overview Schema Source Related Servers Discussions Admin

iconmap_get

Read-only

Retrieve icon maps used on Zabbix network maps; optionally include mapping rules to see how hosts receive icons from inventory fields.

Instructions

Retrieve icon maps used on network maps. Icon maps automatically assign icons to map elements based on host inventory field values. For example, map a host's 'type' inventory field so that routers, switches, and servers each display a distinct icon. Use selectMappings to include the mapping rules in the response.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Maximum number of results to return.
`filter`	No	Return 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: default_iconid, iconmapid, name. Text properties cannot be filtered; use 'search' for them.
`output`	No	Properties of the iconmap 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: iconmapid, name. Properties: default_iconid, iconmapid, name.
`search`	No	Return results whose string properties contain the given pattern (case-insensitive; '*' is a wildcard when searchWildcardsEnabled is true). Example: {"name": "web"}. Keys: name.
`server`	No	Target Zabbix server. Available: default. Defaults to 'default' if omitted.
`raw_json`	No	Strips 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.
`sortfield`	No	Sort by one or more of: iconmapid, name (comma-separated for several; pair with 'sortorder'). No other property is sortable.
`sortorder`	No	Sort order: 'ASC' (ascending) or 'DESC' (descending).
`iconmapids`	No	Return only icon maps with the given IDs.
`countOutput`	No	Return the count of matching results instead of the actual data.
`searchByAny`	No	If true, return results matching ANY search field (OR). Default is ALL fields (AND).
`extra_params`	No	Other native iconmap.get parameters, merged into the request as-is. Parameters: sysmapids. Sub-object selects (value 'extend', 'count' or a list of property names): selectMappings. 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.
`searchWildcardsEnabled`	No	If true, enable * and ? wildcards in search patterns.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.41.0Oct 20, 2026

TDQS

A3.7/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds useful conceptual context about what icon maps do but discloses no behavior beyond that (no auth needs, rate limits, or response-shape caveats); the notable raw_json/disclaimer behavior lives only in the schema.

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?

Three sentences with the purpose front-loaded, followed by a clarifying definition and a concrete example. Every sentence pulls weight, though the example sentence is somewhat illustrative rather than operationally necessary.

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

Completeness4/5

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

With an output schema present and 100% parameter coverage, the description needn't explain return values or parameter mechanics. It supplies enough conceptual context to call the tool correctly, with only minor behavioral gaps remaining.

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%, so the schema itself documents all 13 parameters thoroughly. The description references selectMappings, adding only marginal meaning over the schema, which is the correct baseline-3 situation.

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 ("Retrieve icon maps used on network maps") and goes further by explaining what an icon map is and giving a concrete router/switch/server example. This clearly distinguishes it from the many other *_get siblings like map_get and image_get, so an agent can identify the resource 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 Guidelines3/5

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

The only usage guidance is "Use selectMappings to include the mapping rules in the response," which is a parameter hint rather than a when-to-use-this-vs-alternatives directive. No exclusion conditions or alternative tools are named, so usage is only implied.

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

Deploy Server