Skip to main content
Glama
Grafana MCP Server
by nks1097

grafana_analisar_orcamento_erro

Analyze an SLO's error budget burn rate over a chosen period to identify risks of SLO violations and support proactive reliability decisions.

Instructions

  1. Analisar queima de orçamento de erro (Error Budget Burn Rate) e riscos de violação de SLO.

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": {
      "slo_id_ou_nome": "<slo_id_ou_nome>"
    },
    "name": "grafana_analisar_orcamento_erro"
  }
}

Input Schema

NameRequiredDescriptionDefault
periodoNo30d
slo_id_ou_nomeYes

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?

No annotations are provided, so the description carries the full burden of behavioral disclosure. It does not state whether the tool is read-only, what permissions are required, what data it accesses, or what the analysis involves beyond the high-level purpose.

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?

The description is a single sentence and front-loads the core purpose, but it begins with an extraneous number ('89.') that adds noise. Apart from that, it is efficient with no redundant wording.

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?

Given the absence of annotations, 0% schema description coverage, and only one required parameter, the description is too minimal. While an output schema exists and return values need not be explained, the lack of parameter details, usage guidance, and behavioral context leaves significant gaps for correct invocation.

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 should explain the parameters. It implicitly links 'SLO' to the required 'slo_id_ou_nome' but does not clarify that it accepts an ID or name, and it entirely omits the 'periodo' parameter (default '30d') and its meaning.

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 specific verb ('analisar') and resource ('queima de orçamento de erro' / error budget burn rate) plus risk of SLO violation. It is clear enough to distinguish the tool's purpose, but it doesn't explicitly differentiate it from sibling tools like grafana_consultar_slos.

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 alternatives (e.g., grafana_consultar_slos). The description only states what it does, leaving the agent to infer appropriate contexts without exclusions or prerequisites.

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