Skip to main content
Glama

panel_tree

Dump the live panel hierarchy under a target panel to inspect IDs, types, layout files, sizes, positions, and text for Deadlock Panorama UI debugging.

Instructions

Dump the live panel hierarchy (id, type, layout file, size, position, text) under a panel.

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": "panel_tree"
  }
}

Input Schema

NameRequiredDescriptionDefault
uiNoauto
depthNo
targetNoroot
max_nodesNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/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. "Live" hints that it queries a running process, but nothing states whether it is read-only, what happens if no game is running, or — critically — that max_nodes (default 400) can truncate the result because the description claims to dump the full hierarchy.

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?

A single front-loaded sentence with no filler, and the parenthetical field list is useful. Its brevity is efficient rather than padding, though it leaves no room for the missing guidance.

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?

An output schema exists, so return values need not be described. However, for a four-parameter introspection tool with zero schema coverage and no annotations, the description omits parameter meaning, depth/truncation semantics, and runtime prerequisites — substantial gaps for an agent to call it correctly.

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 explain the four parameters, and it does not. "Under a panel" loosely gestures at target/depth, but ui (default "auto"), depth (default 3), and max_nodes (default 400) are left undefined with no format or bound information.

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?

"Dump the live panel hierarchy ... under a panel" gives a specific verb and resource and enumerates the dumped fields (id, type, layout file, size, position, text). It does not distinguish this from siblings such as panel_find or ui_files, so it stops 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?

The description says nothing about when to use this versus panel_find, ui_files, or ui_source, and gives no preconditions (e.g. game must be running for a *live* tree). Usage must be inferred 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.