Skip to main content
Glama
Grafana MCP Server
by nks1097

grafana_excluir_fonte_dados

Deletes a Grafana data source by UID and requires a two-step approval token to confirm the destructive action.

Instructions

  1. Excluir uma fonte de dados (Ação destrutiva - requer aprovação em dois passos).

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>"
    },
    "name": "grafana_excluir_fonte_dados"
  }
}

Input Schema

NameRequiredDescriptionDefault
uidYes
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

B3/5.0
Behavior3/5

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

With no annotations, the description carries the full load and does disclose the two key behavioral facts: the operation is destructive and requires a two-step approval. It stops short of stating irreversibility, what dependencies break, permission requirements, or how the approval token is obtained/consumed, so transparency is partial.

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, so nothing is padded, but the '25.' prefix is wasted characters and the destructive warning is buried in parentheses rather than front-loaded. Structure is adequate but not optimized.

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 destructive, un-annotated tool with an unexplained approval-token parameter, the description does far too little: an agent cannot learn the irreversibility, the approval workflow steps, or which sibling tools are affected. The presence of an output schema covers return values, but the pre-call behavior gap remains large.

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 largely does not: 'uid' is never described as the data source identifier, and 'token_aprovacao' is only obliquely referenced by the 'aprovação em dois passos' phrase with no explanation of its format, source, or lifetime.

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 and resource ('Excluir uma fonte de dados'), which cleanly distinguishes it from siblings like grafana_atualizar_fonte_dados, grafana_criar_fonte_dados and grafana_obter_fonte_dados. The leading sequence number '25.' is noise that adds no clarity, and no explicit sibling differentiation is written out.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives useful invocation context ('Ação destrutiva - requer aprovação em dois passos'), which tells the agent the deletion cannot be completed in a single call. However, it never says when to prefer deletion over alternatives, nor what prerequisites or pre-checks (e.g. dashboards referencing the data source) should precede 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