Skip to main content
Glama
Grafana MCP Server
by nks1097

grafana_gerar_resumo_pos_incidente

Generate a structured post-mortem and root cause analysis report for an incident from its ID, with markdown as the default output format.

Instructions

  1. Gerar relatório estruturado de Post-Mortem e análise de causa raiz (RCA) de incidente.

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_gerar_resumo_pos_incidente"
  }
}

Input Schema

NameRequiredDescriptionDefault
formatoNomarkdown
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?

Since no annotations are provided, the description carries the full burden of behavioral disclosure. It does not detail operational constraints, such as required input formats for 'incidente_id', rate limits, or specific structural requirements for a successful generation, making it low in transparency.

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 definition is concise and highly focused on the core function of generating the specific type of report required. While the prefix '90.' is unnecessary noise, the core message is efficient.

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?

While it accurately identifies the target use case (Post-Mortem/RCA), the definition is incomplete regarding practical usage. It fails to contextualize the required input parameters or mention potential limitations, relying entirely on the user's domain knowledge.

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?

With schema description coverage at 0%, the description must provide significant semantic value, but it does not. It only lists the general purpose of the tool without explaining the format options ('formato') or the expected characteristics of the 'incidente_id' beyond what the schema dictates.

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 clearly identifies the specific resource and purpose: generating a structured report focusing on Post-Mortem and Root Cause Analysis (RCA) of an incident. This specific focus differentiates it from generic reporting siblings like `grafana_gerar_relatorio_desempenho`.

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 states what the tool does but offers no guidance on when it should be used versus other available reporting tools. There are no 'when/when-not' scenarios provided, leading to potential overlap with other incident-related report generation tools.

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