Skip to main content
Glama
initMAX

Zabbix MCP Server

sla_get

Read-only

Retrieve SLA definitions to inspect SLO targets, schedules, and service links for Zabbix availability monitoring.

Instructions

Retrieve SLA definitions. SLAs measure service availability against defined targets (e.g. 99.9% uptime). Each SLA has a schedule, SLO (Service Level Objective) percentage, and is linked to services via service tags. Use selectServiceTags, selectExcludedDowntimes, and selectSchedule in extra_params to include related objects.

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: description, effective_date, name, period, slaid, slo, status, timezone. Text properties cannot be filtered; use 'search' for them.
outputNoProperties of the sla 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: slaid, name, slo, status. Properties: description, effective_date, name, period, slaid, slo, status, timezone.
searchNoReturn results whose string properties contain the given pattern (case-insensitive; '*' is a wildcard when searchWildcardsEnabled is true). Example: {"name": "web"}. Keys: description, name, timezone.
serverNoTarget Zabbix server. Available: default. Defaults to 'default' if omitted.
slaidsNoReturn only SLAs with the given IDs.
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: slaid, name, period, slo, effective_date, timezone, status, description (comma-separated for several; pair with 'sortorder'). No other property is sortable.
sortorderNoSort order: 'ASC' (ascending) or 'DESC' (descending).
serviceidsNoReturn only SLAs linked to the given services.
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 sla.get parameters, merged into the request as-is. Sub-object selects (value 'extend', 'count' or a list of property names): selectExcludedDowntimes, selectSchedule, selectServiceTags. 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

A3.5/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 domain context but says nothing about pagination, default result size, or how the limit/output interact, leaving the behavioral burden mostly on structured fields.

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?

Front-loaded with the verb and resource, followed by two compact sentences of domain context and one usage tip. No filler, though the SLA-definition gloss is more educational than operational.

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 full annotation coverage, the description need not explain return values. It supplies enough domain framing to understand what is being fetched, though it stops short of routing the agent away from closely named siblings.

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 already documents all 14 parameters thoroughly. The description only reiterates the extra_params sub-selects already spelled out in the schema, adding no meaningful semantics beyond it. 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?

States a clear verb+resource ('Retrieve SLA definitions') and adds a domain gloss explaining what an SLA is (availability targets, schedule, SLO, service-tag linkage). It does not, however, distinguish itself from the sibling sla_getsli, which an agent could plausibly confuse it with.

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?

Offers one concrete usage hint (use selectServiceTags/selectExcludedDowntimes/selectSchedule in extra_params to include related objects), but gives no when-to-use vs when-to-use-alternative guidance and no exclusions relative to sla_getsli or service_get.

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