Skip to main content
Glama
Grafana MCP Server
by nks1097

grafana_atualizar_pasta

Updates the title or properties of an existing Grafana folder, letting teams rename or adjust folder metadata without recreating it.

Instructions

  1. Atualizar o título ou propriedades de uma pasta existente.

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": {
      "uid": "<uid>",
      "novo_titulo": "<novo_titulo>"
    },
    "name": "grafana_atualizar_pasta"
  }
}

Input Schema

NameRequiredDescriptionDefault
uidYes
novo_tituloYes

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: it says 'update' but not whether the change is reversible, whether permissions are required, whether unspecified properties are preserved, or what happens on a missing folder. For a mutation tool with zero annotation coverage this is a significant gap.

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 short sentence keeps it tight, but the leading '63.' is leftover numbering noise that adds no value and slightly degrades front-loading.

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?

An output schema exists so return values need not be explained, but with no annotations, 0% parameter documentation, and an unsupported 'propriedades' claim, the definition leaves an agent without enough to call it correctly in edge cases.

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 does not. It implies a title parameter but never explains that 'uid' identifies the target folder or that it is required and immutable, and never clarifies the 'novo_titulo' semantics beyond 'title'.

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 (Atualizar) and resource (pasta existente) plus the fields touched (título/propriedades), which distinguishes it from criar_pasta and excluir_pasta by name. However, 'propriedades' is not backed by any schema parameter, so the stated scope overreaches the actual capability.

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?

No guidance on when to use this versus grafana_criar_pasta or grafana_mover_dashboard, no prerequisites such as needing the folder's uid to exist, and no note about what happens if the uid is invalid. Usage must be inferred entirely from the name.

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