Skip to main content
Glama
Grafana MCP Server
by nks1097

grafana_adicionar_atividade_incidente

Add notes, actions, or comments directly to a Grafana incident timeline so teams can document progress and keep investigation context in one place.

Instructions

  1. Adicionar notas, ações ou comentários na linha do tempo de um 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>",
      "mensagem": "<mensagem>"
    },
    "name": "grafana_adicionar_atividade_incidente"
  }
}

Input Schema

NameRequiredDescriptionDefault
mensagemYes
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.6/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden and does not meet it. It conveys that this is an append action on an incident timeline, but says nothing about whether the incident must exist or be in a particular state, what permissions are required, whether entries are immutable once posted, or what a successful response contains (the output schema covers returns, but the 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.

Conciseness3/5

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

A single compact sentence with no padding beyond the numeric prefix "85.", which is an artifact rather than information. It is efficient but very thin for a mutation tool with two required params.

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 write operation with zero annotations and 0% schema coverage, the description leaves out preconditions, side effects, and payload expectations. The existence of an output schema relieves it of explaining return values, but the operational context an agent needs before calling it is largely missing.

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%, so the description must compensate, and it only partly does: "notas, ações ou comentários" loosely characterizes the mensagem payload as free-form text and "de um incidente" implies incidente_id. Neither parameter's format (IDs, length limits, markdown support) is clarified.

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 ("Adicionar") and a specific resource ("notas, ações ou comentários na linha do tempo de um incidente"), which distinguishes it from the read-only timeline generator in the sibling list. It does not explicitly name any sibling or state exclusions, 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?

There is no when-to-use guidance, no prerequisites, and no mention of alternatives such as grafana_atualizar_incidente (which likely changes incident fields) versus this tool (which appends timeline entries). An agent must infer the usage context entirely from the phrase "linha do tempo".

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