Skip to main content
Glama
Zabbix MCP Server

Zabbix MCP Server

token_get

Read-only

Retrieve Zabbix API tokens for persistent authentication of scripts, integrations, and service accounts without user.login sessions; filter, sort, and select returned properties.

Instructions

Retrieve API tokens. Tokens provide persistent authentication for scripts, integrations, and service accounts without requiring user.login sessions. Each token is bound to a specific user and inherits that user's permissions. Tokens have optional expiry dates and can be enabled or disabled independently.

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: created_at, creator_userid, expires_at, lastaccess, name, status, tokenid, userid. Text properties cannot be filtered; use 'search' for them.
outputNoProperties of the token object to return. Pass 'extend' for all, 'count' for the number of matches only, or a list of property names. Default when omitted: tokenid, name, userid, status, expires_at. Properties: created_at, creator_userid, description, expires_at, lastaccess, name, status, tokenid, userid.
searchNoReturn results whose string properties contain the given pattern (case-insensitive; '*' is a wildcard when searchWildcardsEnabled is true). Example: {"name": "web"}. Keys: description, 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.
tokenidsNoReturn only tokens with the given IDs.
sortfieldNoSort by one or more of: tokenid, name, lastaccess, status, expires_at, created_at (a list 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).
extra_paramsNoOther native token.get parameters, merged into the request as-is. Parameters: expired_at, token, userids, valid_at. 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. Changed10 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": [
      +        "excludeSearch",
      +        "preservekeys",
      +        "startSearch",
      +        "expired_at",
      +        "token",
      +        "userids",
      +        "valid_at"
      +      ]
      +    },
      +    "type": "object"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedInput schema / properties / filter / anyOf
      Previous value: -[
      -  {
      -    "additionalProperties": true,
      -    "type": "object"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "propertyNames": {
      +      "enum": [
      +        "created_at",
      +        "creator_userid",
      +        "expires_at",
      +        "lastaccess",
      +        "name",
      +        "status",
      +        "tokenid",
      +        "userid"
      +      ]
      +    },
      +    "type": "object"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedInput schema / properties / output / anyOf
      Previous value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "enum": [
      +      "extend",
      +      "count"
      +    ],
      +    "type": "string"
      +  },
      +  {
      +    "items": {
      +      "enum": [
      +        "created_at",
      +        "creator_userid",
      +        "description",
      +        "expires_at",
      +        "lastaccess",
      +        "name",
      +        "status",
      +        "tokenid",
      +        "userid"
      +      ],
      +      "type": "string"
      +    },
      +    "minItems": 1,
      +    "type": "array"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedInput schema / properties / output / description
      Previous value: -"Properties of the token 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: tokenid, name, userid, status, expires_at. Properties: created_at, creator_userid, description, expires_at, lastaccess, name, status, tokenid, userid."New value: +"Properties of the token object to return. Pass 'extend' for all, 'count' for the number of matches only, or a list of property names. Default when omitted: tokenid, name, userid, status, expires_at. Properties: created_at, creator_userid, description, expires_at, lastaccess, name, status, tokenid, userid."
    • changedInput schema / properties / search / anyOf
      Previous value: -[
      -  {
      -    "additionalProperties": true,
      -    "type": "object"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "propertyNames": {
      +      "enum": [
      +        "description",
      +        "name"
      +      ]
      +    },
      +    "type": "object"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedInput schema / properties / sortfield / anyOf
      Previous value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "enum": [
      +      "tokenid",
      +      "name",
      +      "lastaccess",
      +      "status",
      +      "expires_at",
      +      "created_at"
      +    ],
      +    "type": "string"
      +  },
      +  {
      +    "items": {
      +      "enum": [
      +        "tokenid",
      +        "name",
      +        "lastaccess",
      +        "status",
      +        "expires_at",
      +        "created_at"
      +      ],
      +      "type": "string"
      +    },
      +    "minItems": 1,
      +    "type": "array"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedInput schema / properties / sortfield / description
      Previous value: -"Sort by one or more of: tokenid, name, lastaccess, status, expires_at, created_at (comma-separated for several; pair with 'sortorder'). No other property is sortable."New value: +"Sort by one or more of: tokenid, name, lastaccess, status, expires_at, created_at (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": "token_getOutput",
      -  "type": "object"
      -}New value: +null
  2. First observedv1.41.0

TDQS

B3.2/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true and openWorldHint=false, covering the safety profile. The description adds useful domain behavior about tokens being user-bound, permission-inheriting, expirable, and independently enabled or disabled, but it omits retrieval-specific details such as required permissions, pagination, or whether secret token values are returned.

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 front-loaded with the core action and then provides four compact sentences of relevant domain context. Every sentence relates to interpreting token records, though the background could be slightly tightened without losing value.

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 token-listing tool with no output schema, the description supplies useful domain context but does not explain the return shape, pagination behavior, or whether actual token secrets are included. The schema handles parameter semantics and annotations handle safety, so this is adequate but not fully complete.

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%, and the schema thoroughly documents all 13 parameters including filter, search, output, sort, and raw_json. The description adds no parameter-level meaning beyond that, so the baseline score of 3 is appropriate.

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, 'Retrieve', and a specific resource, 'API tokens', so the tool's core purpose is immediately clear. It does not explicitly contrast with sibling retrieval tools such as user_get or role_get, though the resource name is sufficiently distinct.

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 explains what API tokens are used for generally, but gives no guidance on when to call token_get versus another retrieval tool, and no exclusions or alternatives are named. The token background is contextual, not actionable usage guidance.

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