Skip to main content
Glama
Sign In
Zabbix MCP Server Universal

Zabbix MCP Server Universal

by nks1097
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

zabbix_consultar_regras_escalonamento

Retrieves the escalation conditions and steps configured for a Zabbix action ID, so you can verify how alerts are escalated.

Instructions

  1. Consultar condições e etapas de escalonamento configuradas.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "actionid": "<actionid>"
    },
    "name": "zabbix_consultar_regras_escalonamento"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionidYes

Output Schema

NameRequiredDescriptionDefault
erroNoDescrição detalhada do erro caso sucesso seja false
dadosNoPayload estruturado retornado pela operação
avisosNoLista de avisos, recomendações ou pendências
sucessoYesIndica se a operação foi bem-sucedida
metadadosNoMetadados operacionais da execução
id_requisicaoNoIdentificador único da requisição para rastreabilidade

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.6/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. 'Consultar' implies a read-only operation, but the description says nothing about permissions, what happens if the actionid has no escalation rules, or whether results include disabled entries — all meaningful for a no-annotation tool.

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?

One short sentence is efficient, but the '57.' numeric prefix is dead weight and the sentence front-loads a list-number rather than the operation. It is concise without being informative.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need not be explained, but the description omits that a mandatory actionid must be supplied and gives no indication of what the escalation configuration contains. For a tool with a required identifier and zero annotation coverage, this leaves important gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, and the single required parameter actionid is never mentioned in the description. Critically, the agent is not told that escalation rules are scoped to a parent action, which is the key semantic the parameter demands.

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 (consult) and a specific resource (escalation conditions and steps/regras de escalonamento), so the agent knows roughly what it retrieves. It does not differentiate itself from nearby siblings such as zabbix_consultar_acoes, which covers overlapping action/escalation territory, and the leading '57.' numbering is noise rather than meaning.

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 contains no when-to-use guidance, no prerequisites, and no mention of alternatives such as zabbix_consultar_acoes or zabbix_gerenciar_acoes. The agent must infer from the name alone when escalation-rule lookup is appropriate.

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

Deploy Server

Other Tools