Skip to main content
Glama
Zabbix MCP Server

Zabbix MCP Server

by mhajder

Sla Get

sla_get
Read-onlyIdempotent

Retrieve Zabbix Service Level Agreements (SLAs) to review uptime and availability targets, track compliance, and page through records by ID, service, or search criteria.

Instructions

Get SLAs from Zabbix.

Service Level Agreements (SLAs) define uptime and availability targets for services. They track compliance with service objectives and generate reports on availability.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "sla_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of results to return. Default is 100.
offsetNoNumber of matching records to skip. Use with 'limit' to page through results; check 'has_more' and 'total' in the response.
outputNoextend
searchNoDictionary with search criteria like {'name': 'Website'}.
slaidsNoList of SLA IDs to get. Omit to return all SLAs; an empty list matches none.
sortfieldNoField to sort by. A deterministic sort is required for paging to be consistent.slaid
sortorderNoSort direction - 'ASC' or 'DESC'.ASC
serviceidsNoList of service IDs to get SLAs for. An empty list matches none.
count_outputNoIf true, returns only the count of matched objects as an integer.
filter_paramsNoAdditional filter parameters for advanced filtering.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.7.1
    • changedInput schema / properties / serviceids / description
      Previous value: -"List of service IDs to get SLAs for."New value: +"List of service IDs to get SLAs for. An empty list matches none."
    • changedInput schema / properties / slaids / description
      Previous value: -"List of SLA IDs to get. If empty, returns all SLAs."New value: +"List of SLA IDs to get. Omit to return all SLAs; an empty list matches none."
  2. Changed5 schema fields changedv0.6.0
    • changedInput schema / properties / offset / description
      Previous value: -"Number of results to skip (for pagination). Requires sortfield to be set."New value: +"Number of matching records to skip. Use with 'limit' to page through results; check 'has_more' and 'total' in the response."
    • removedInput schema / properties / sortfield / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • changedInput schema / properties / sortfield / default
      Previous value: -nullNew value: +"slaid"
    • changedInput schema / properties / sortfield / description
      Previous value: -"Field to sort by."New value: +"Field to sort by. A deterministic sort is required for paging to be consistent."
    • addedInput schema / properties / sortfield / type
      Added value: +"string"
  3. First observedv0.5.3

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so safety is fully covered structurally. The description adds only background about what SLAs conceptually are, not how the tool behaves — nothing about paging, the count_output mode, sort determinism, or response shape (even though an output schema exists, the paging/count interaction is behavioral context the schema's parameter docs only partially cover).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The lead sentence is front-loaded and useful; the two following sentences are domain tutorial content that doesn't help an agent invoke the tool. Appropriately short, but with waste.

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?

With an output schema and near-complete parameter docs, an agent can call this correctly. What's missing is the sibling routing context (service_get vs sla_get) and any behavioral note on the two output modes.

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 90%, so limit, offset, slaids, serviceids, count_output and sortfield are already well documented in the schema. The description adds no parameter meaning beyond that; 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 specific verb and resource ("Get SLAs from Zabbix") and the definitional sentence clarifies what an SLA is. However, it does nothing to distinguish this from the closely-related sibling service_get, which also retrieves availability objects.

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 indication of when to use this versus service_get, nor any prerequisite or exclusion guidance. The only implied usage is 'retrieve SLAs', which the name already conveys.

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