Skip to main content
Glama

panel_delete

Delete a live panel by id (e.g. one created with xml_load). The UI root, the bridge panel and its ancestors are refused.

Instructions

Delete a live panel by id (e.g. one created with xml_load). The UI root, the bridge panel and its ancestors are refused.

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": {
      "target": "<target>"
    },
    "name": "panel_delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
uiNoauto
targetYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations at all, the description must carry the full behavioral burden. It usefully discloses that certain panels are refused, which is real behavioral context, but it omits whether deletion is irreversible, whether confirmation is required, and what permissions or side effects apply to a live panel.

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

Conciseness4/5

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

Two tightly written sentences, front-loaded with the core action and followed by the refusal constraint. No filler or redundant phrasing; minor room to compress further but nothing distracting.

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

Completeness3/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 needn't be explained, and the protected-panel rule is covered. However, for a destructive tool with no annotations, it should say more about irreversibility, the role of the 'ui' parameter, and any preconditions for a valid target.

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 is the only source of parameter meaning. It identifies 'target' as a panel id but says nothing about the 'ui' parameter (default 'auto') or the expected id format, leaving half the parameters unexplained.

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: 'Delete a live panel by id', with a concrete example of origin ('one created with xml_load'). This clearly distinguishes it from creation and inspection siblings like xml_load and panel_tree, though it doesn't name an alternative deletion path.

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?

The description establishes context (panels created via xml_load) and refusal conditions (UI root, bridge panel, ancestors), which guides safe use. It does not say when to prefer it over other tools or how to locate a valid id, leaving that largely implied.

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