Skip to main content
Glama
Grafana MCP Server
by nks1097

grafana_atualizar_incidente

Update an operational incident's status (e.g., investigating, mitigated, resolved) and optional summary in Grafana to keep response tracking accurate.

Instructions

  1. Atualizar status de incidente operacional (ex: 'investigating', 'mitigated', 'resolved').

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": {
      "incidente_id": "<incidente_id>"
    },
    "name": "grafana_atualizar_incidente"
  }
}

Input Schema

NameRequiredDescriptionDefault
resumoNo
statusNo
incidente_idYes

Output Schema

NameRequiredDescriptionDefault
erroNoMensagem de erro amigável caso haja falha
dadosNoCarga útil da resposta estruturada
avisosNoLista de alertas e avisos operacionais
sucessoNoIndica se a operação foi bem-sucedida
metadadosNoMetadados da execução
id_requisicaoNoIdentificador único da operação

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.8/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 disclosure burden for a mutation tool. It never says whether the status change triggers notifications/on-call pages, whether it requires the incident to be in a particular state, whether it is idempotent, or what happens to the optional 'resumo' field — significant gaps for a state-changing operation.

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?

It is a single compact sentence with no wasted clauses, and the actionable content is front-loaded. The stray '84.' prefix is a formatting defect that does not belong in agent-facing text and slightly hurts structure.

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?

For a 3-parameter mutation tool with zero annotation coverage and zero schema description coverage, the description is too thin. An output schema exists, so return values need not be explained, but the missing side-effect disclosure and the undocumented 'resumo' parameter leave real 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% across 3 parameters, so the description must compensate. It only partially does so: the example status strings document the 'status' field's expected vocabulary, but 'incidente_id' (the sole required param) and 'resumo' receive no explanation of format or purpose anywhere.

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 clear verb+resource ('Atualizar status de incidente operacional') and enumerates example status values, so an agent immediately knows this changes incident state. It does not, however, distinguish itself from nearby siblings like grafana_adicionar_atividade_incidente or grafana_obter_incidente, and the leading '84.' is a numbering artifact that adds noise.

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?

Usage is implied by the example statuses ('investigating', 'mitigated', 'resolved'), which signal the intended lifecycle-update scenario. There is no explicit statement of when to prefer this over grafana_adicionar_atividade_incidente or grafana_gerar_resumo_pos_incidente, and no prerequisites or exclusions are given.

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