Skip to main content
Glama
Grafana MCP Server
by nks1097

grafana_gerenciar_equipes

Create, update, or delete Grafana teams with approval-token control to manage team access safely.

Instructions

  1. Criar, atualizar ou excluir equipes no Grafana com controle de aprovação.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "grafana_gerenciar_equipes"
  }
}

Input Schema

NameRequiredDescriptionDefault
acaoNoconsultar
nomeNo
emailNo
team_idNo
token_aprovacaoNo

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
Behavior3/5

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

With zero annotations, the description carries the full disclosure burden. It does add one genuinely useful behavioral fact — operations are subject to approval control — which explains the token_aprovacao parameter's existence. However, it never states what happens on delete (destructive and irreversible?), what permissions are required, or what the approval flow looks like in practice.

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 sentence with no filler, which is good, but the leading '95.' is pure noise and the sentence is too short for the tool's complexity. The operative content is front-loaded, but there is not enough of it.

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?

This is a multi-action mutation tool with five undocumented, all-optional parameters and no annotations. An output schema exists so return values need not be explained, but the input contract — which combination of acao/team_id/nome/email/token_aprovacao is valid for each action — is left entirely unaddressed, which is a serious gap for a create/update/delete tool.

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% across five parameters, so the description must compensate and largely fails to. It never enumerates the accepted values of acao (criar/atualizar/excluir/consultar), never says that team_id identifies the target team, and only indirectly gestures at token_aprovacao via 'controle de aprovação'. nome and email are entirely undocumented.

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 three specific verbs (criar, atualizar, excluir) against a specific resource (equipes no Grafana), so the agent immediately knows the operation class. It does not differentiate from the sibling grafana_listar_equipes, which handles the read path, so the boundary is left implicit.

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 pointer to grafana_listar_equipes for read-only team queries even though 'consultar' appears as the default value of acao. The phrase 'com controle de aprovação' hints at a gated workflow but never explains what triggers it or how to satisfy it.

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