Skip to main content
Glama

remove_panel

Destructive

Remove one panel by id and save a report version. Use when deleting a chart or KPI from a dashboard.

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": {
      "reportId": "<reportId>",
      "panelId": "<panelId>"
    },
    "name": "remove_panel"
  }
}

Input Schema

NameRequiredDescriptionDefault
panelIdYesPanel id
reportIdYesReport id
expectedVersionNoThe report `version` your edit is based on, from get_report or the last save. The save is rejected if the report changed since. Omit to apply your change to the latest version.

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is known. The description adds real value beyond them by disclosing that the removal persists a new report version, which is a side effect an agent might not otherwise anticipate. It could say more about irreversibility or interaction with expectedVersion conflict, but the schema covers the latter.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences, front-loaded with the action and its side effect, followed by the triggering scenario. Nothing is wasted and no clause is redundant.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a three-parameter destructive tool, the description covers what it does, the persistence side effect, and when to reach for it, while annotations carry danger and the schema carries versioning semantics. No output schema exists, but the return shape (a saved report version) is implied adequately.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so panelId, reportId, and expectedVersion are fully documented in the schema, including the optimistic-concurrency behavior. The description only echoes "by id" and adds no new parameter meaning, which is the baseline for fully-covered schemas.

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 ("Remove one panel by id") and adds the consequential side effect ("save a report version"), which is more than the name conveys. It does not explicitly contrast with update_panel or add_panel, but the remove semantics are unambiguous.

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

Usage Guidelines4/5

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

"Use when deleting a chart or KPI from a dashboard" gives clear situational context for invocation. It stops short of exclusions — e.g. whether to use update_panel instead when merely hiding or reconfiguring a panel — so the guidance is contextual rather than complete.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources