Skip to main content
Glama
Zabbix MCP Server Universal

Zabbix MCP Server Universal

by nks1097

zabbix_atualizar_manutencao

Updates an authorized Zabbix maintenance window by ID, allowing changes to its end time or description.

Instructions

  1. Alterar uma janela de manutenção autorizada.

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": {
      "maintenanceid": "<maintenanceid>"
    },
    "name": "zabbix_atualizar_manutencao"
  }
}

Input Schema

NameRequiredDescriptionDefault
active_tillNo
descriptionNo
maintenanceidYes

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/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It does not state that this is a mutating operation, whether unspecified fields are left untouched (partial vs full update), what permissions are required, or what happens with an invalid maintenanceid. The presence of an output schema covers the return side, but mutation semantics are undisclosed.

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

Conciseness2/5

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

The sentence is short but wastes its opening on a list-style number ("68.") and carries almost no information beyond the tool name. Brevity here comes from under-specification rather than efficiency.

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

Completeness1/5

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

For a mutation tool with zero annotation coverage, zero schema description coverage, and an ambiguous timestamp parameter, the description provides nothing an agent needs to invoke it correctly. Only the existence of an output schema offsets any of the burden.

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

Parameters1/5

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

Schema description coverage is 0% across 3 parameters, so the description must compensate and it does not — active_till, description, and maintenanceid are never mentioned or explained. In particular, the format of active_till (Unix timestamp?) is left entirely ambiguous.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The verb+resource pair "Alterar uma janela de manutenção" does identify an update operation on a maintenance window, which distinguishes it from zabbix_criar_manutencao and zabbix_listar_manutencoes by name alone. However the qualifier "autorizada" is unexplained, the stray "68." prefix is noise, and the description says nothing about what aspects of the window are altered.

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 guidance on when to use this tool versus zabbix_criar_manutencao, zabbix_consultar_* or the sibling listing tool. The agent must infer that an existing maintenanceid is a precondition and that creation is handled elsewhere.

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