Skip to main content
Glama
Grafana MCP Server
by nks1097

grafana_gerenciar_permissoes_dashboard

Updates the access control list (ACL) for a specific Grafana dashboard by replacing its permission entries.

Instructions

  1. Atualizar a lista de permissões (ACL) de um dashboard específico.

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": {
      "dashboard_uid": "<dashboard_uid>",
      "itens_permissao": "<itens_permissao>"
    },
    "name": "grafana_gerenciar_permissoes_dashboard"
  }
}

Input Schema

NameRequiredDescriptionDefault
dashboard_uidYes
itens_permissaoYes

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 burden: it doesn't say whether this replaces the entire ACL or merges with existing entries, what admin/org-role permissions are required, or whether changes are reversible. "Atualizar a lista" hints at replacement semantics, but this is not stated explicitly and is a consequential ambiguity for a security-sensitive mutation.

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 efficient sentence with the resource front-loaded, but the leading "97." enumeration artifact is noise that signals a machine-generated list rather than a deliberate definition. Nothing else is wasted, but nothing is added either.

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 mutation tool with no annotations, an opaque nested-array parameter, and 0% schema documentation, the description is far too thin. The output schema means return values needn't be explained, but the payload contract and permission requirements are essential missing context.

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 doesn't. The critical parameter itens_permissao is an array of free-form objects (additionalProperties: true), and the description gives no hint about the expected fields (userId, teamId, role, permission level) or accepted values, leaving the agent to guess the payload shape.

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 concrete verb ("Atualizar") and resource ("lista de permissões (ACL) de um dashboard específico"), which is enough to tell it apart from the folder-level ACL sibling grafana_gerenciar_permissoes_pasta. It does not explicitly name the sibling or explain the distinction, 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 guidance on when to use this tool versus alternatives such as grafana_consultar_permissoes (read) or grafana_gerenciar_permissoes_pasta (folder scope), nor are prerequisites or the consequences of updating an ACL mentioned. The agent must infer the usage context 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