Skip to main content
Glama
Zabbix MCP Server

Zabbix MCP Server

by mhajder

Service Get

service_get
Read-onlyIdempotent

Retrieves Zabbix services representing business capabilities and applications, with filtering, search, and paging. Use it to map service hierarchies and track dependencies.

Instructions

Get services from Zabbix.

Services represent business capabilities or applications (e.g., 'Web Application', 'Database'). Services can depend on other services, creating hierarchies for tracking dependencies.

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": "service_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': 'API'}.
parentidsNoList of parent service IDs to get child services from. An empty list matches none.
sortfieldNoField to sort by. A deterministic sort is required for paging to be consistent.serviceid
sortorderNoSort direction - 'ASC' or 'DESC'.ASC
serviceidsNoList of service IDs to get. Omit to return all services; 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 / parentids / description
      Previous value: -"List of parent service IDs to get child services from."New value: +"List of parent service IDs to get child services from. An empty list matches none."
    • changedInput schema / properties / serviceids / description
      Previous value: -"List of service IDs to get. If empty, returns all services."New value: +"List of service IDs to get. Omit to return all services; 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: +"serviceid"
    • 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

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds useful domain context about service hierarchies, but does not disclose operational behavior such as pagination, auth requirements, or response shape beyond what the schema and output schema provide.

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 short, front-loaded, and appropriately sized. The first sentence identifies the operation, and the following sentences explain the resource domain. The generic service explanation is useful but not strictly necessary, keeping it just below maximally concise.

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 10 optional parameters, 90% schema description coverage, an output schema, and read-only annotations, the description does not need to restate parameter or return details. It could be more complete by mentioning paging/counting or when to choose this over other retrieval tools, but the structured metadata covers most requirements.

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 the schema already documents nearly all parameters, including limit, offset, search, parentids, serviceids, sortfield, sortorder, and count_output. The description adds no parameter-specific meaning beyond the schema, which is acceptable at the baseline for high-coverage schemas.

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 and resource: 'Get services from Zabbix.' It also clarifies that services are business capabilities/applications and can form dependency hierarchies, which helps distinguish this from other *_get tools. It does not explicitly name sibling alternatives, so it falls short of a 5.

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 says what the tool retrieves but gives no explicit guidance on when to use it versus alternatives, nor when to use specific parameters such as parentids, search, count_output, or paging options. Usage is only implied by the tool name and resource domain.

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