gmod-mcp

inspect_panel

Find a Garry's Mod VGUI panel by its registered name, class, or displayed text. Returns screen rectangle, text content, keyboard focus status, and other matching panels.

Instructions

Finds a panel by NAME, class and/or displayed text, and returns its screen rectangle, its text, whether it holds keyboard focus, and the other matches. NAME is the registered vgui name (R_CharCreate, R_UI_Button, echat.textentry) and is what you want: class is the VGUI base the panel derives from, so a kit panel's class reads Label or Panel and searching by class can never find it. Off-screen panels are excluded unless onScreen:false -- a live tree measured 1408 panels of which 5 were on screen.

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

Input Schema

Name	Required	Description
`name`	No	Registered vgui name, e.g. R_UI_Button. Exact match.
`class`	No	VGUI base class, e.g. Label, Panel, TextEntry. Exact match.
`index`	No	Which match to return when several qualify.
`contains`	No	Substring of the panel's displayed text, case-insensitive -- 'the button that says ÉCROUER'.
`onScreen`	No	Keep only panels whose whole ancestry is visible. false includes closed menus.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.0.0Jul 29, 2026

TDQS

A4.5/5.0

Behavior4/5

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

With no annotations beyond title, the description carries the full burden. It discloses return values (rectangle, text, focus, other matches) and behavior (excludes off-screen panels unless onScreen:false). It does not explicitly state it is read-only, but the find-and-return nature strongly implies no side effects. The practical statistic adds context.

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?

The description is a single dense paragraph that packs all necessary information without redundancy. It is front-loaded with the core action and progressively adds detail. No wasted sentences; every clause earns its place.

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?

The description covers all parameters and return fields explicitly (rectangle, text, focus, other matches). It lacks an output schema but compensates by naming the return fields. It could mention error behavior when no panel is found, but this is minor. For a simple inspection tool, it is sufficiently complete.

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

Parameters5/5

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

Schema coverage is 100% with good descriptions, but the tool description adds significant value: it explains the vgui name concept with examples, clarifies that class is the base type and often generic (e.g., Label, Panel), and interprets the index and contains parameters. This enriches understanding beyond schema alone.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description explicitly states it finds a panel by name, class, or displayed text and returns detailed info (rectangle, text, focus, other matches). It clearly distinguishes NAME (registered vgui name) from class (base class), making the purpose unmistakable and differentiating it from sibling tools like read_panels.

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?

The description provides clear guidance: 'NAME is what you want' and warns that searching by class is unhelpful. It also explains the onScreen parameter behavior. However, it does not explicitly mention when to use this tool over siblings (e.g., read_panels for listing), though the context is implied.

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