Skip to main content
Glama
initMAX

Zabbix MCP Server

valuemap_get

Read-only

Retrieve value maps that translate numeric item values into human-readable strings (e.g., 0 -> 'Down', 1 -> 'Up').

Instructions

Retrieve value maps. Value maps translate numeric item values into human-readable strings (e.g., 0 -> 'Down', 1 -> 'Up'). They are defined on hosts or templates and referenced by items for display purposes.

Input Schema

TableJSON 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: hostid (6.0+), name, uuid (6.0+), valuemapid. Text properties cannot be filtered; use 'search' for them.
outputNoProperties of the valuemap 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: valuemapid, name. Properties: hostid (6.0+), name, uuid (6.0+), valuemapid.
searchNoReturn results whose string properties contain the given pattern (case-insensitive; '*' is a wildcard when searchWildcardsEnabled is true). Example: {"name": "web"}. Keys: name, uuid (6.0+).
serverNoTarget Zabbix server. Available: default. Defaults to 'default' if omitted.
hostidsNoReturn only value maps that belong to the given hosts or templates.
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: valuemapid, name (comma-separated for several; pair with 'sortorder'). No other property is sortable.
sortorderNoSort order: 'ASC' (ascending) or 'DESC' (descending).
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).
valuemapidsNoReturn only value maps with the given IDs.
extra_paramsNoOther native valuemap.get parameters, merged into the request as-is. 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.
searchWildcardsEnabledNoIf true, enable * and ? wildcards in search patterns.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.41.0

TDQS

B3.2/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 and the bar is lower. The description adds useful domain context (value maps are host/template-scoped and consumed by items), but says nothing about pagination, permission requirements, or result ordering behavior.

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 short sentences, front-loaded with the action and then the object definition. Nothing is wasted, though the parenthetical example and the host/template sentence lean slightly toward encyclopedic background rather than operational content.

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?

An output schema exists and the annotations cover the safety profile, so the description does not need to explain return values. The parameter surface is fully documented in the schema. The only remaining gap is the absence of any scope/filtering or routing note, which is minor for a straightforward list tool.

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% across all 14 parameters, so the schema itself documents limit, filter, output, search, hostids, raw_json, sorting, and the rest in detail. The description contributes no parameter-level meaning beyond that, so the baseline 3 applies.

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 opens with a specific verb+resource ("Retrieve value maps") and then defines the domain object concretely, including where value maps live (hosts/templates) and how they are used (item display). That is clear enough for an agent to know what it will get. It stops short of a 5 because it never distinguishes itself from sibling lookup tools such as iconmap_get, regexp_get, or item_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?

There is no when-to-use or when-not-to-use guidance and no alternative tool is named. The background sentence about value maps being "referenced by items for display purposes" is definitional, not a routing rule, so an agent still has to infer the retrieval scenario on its own.

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