Skip to main content
Glama

read_panel_text

Reads text from Garry's Mod UI panels to assert values, extracting text from GetText, GetValue, or label fields. Filters by visibility and depth.

Instructions

Dumps what the interface DISPLAYS, as text: name, class, screen rectangle and text content of each panel under a named root. Use this instead of capture_screen to assert a value -- a capture travels in 7KB chunks paced one per frame, and a number read off a compressed JPEG is not an assertion. Text comes from GetText, GetValue, or a .label/.text/.title field (kit buttons paint their label and answer '' to GetText). The list is depth-first with depth relative to the root, so the parent chain is recoverable from the ordering: the DTextEntry that follows the DLabel 'Prénom' is that field. capture_screen remains the tool for anything visual -- z-order, overlap, a missing glyph.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
rootNoPanel to dump from, matched as a NAME first then as a class. Omitted, dumps the whole screen.
indexNoWhich root when several match.
limitNoMaximum entries; the rest are counted in `truncated`.
maxDepthNoDepth below the root.
onScreenNoSkip panels whose ancestry is hidden.
onlyTextNoSkip panels carrying no text. false dumps the structure too.
Behavior5/5

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

The description discloses multiple behavioral traits beyond the minimal annotations: explains text sources (GetText, GetValue, .label/.text/.title fields), caveat about kit buttons painting their label and returning empty to GetText, and the depth-first ordering with parent-chain recoverability. Annotations only provide a title, so the description carries full burden and excels.

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?

The description is moderately long but each sentence adds distinct value: purpose, usage guidance, behavioral nuances, ordering explanation. It is well-structured and front-loaded with the main purpose. A slight trim could be possible (e.g., combining the kit button note), but overall it earns its length.

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?

Given the tool has 6 parameters and no output schema, the description adequately covers the tool's purpose, usage, text sources, and ordering. It lacks an explicit description of the output format (e.g., JSON structure) but compensates by explaining the ordering and what information is dumped. It is sufficient for an agent to use correctly.

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 the baseline is 3. The description does not add extra information about individual parameters beyond what the schema already provides. It provides context about the tool's behavior (e.g., text sources) but no parameter-specific clarifications.

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 uses the verb 'Dumps' with a clear resource: 'what the interface DISPLAYS, as text: name, class, screen rectangle and text content of each panel under a named root.' It clearly distinguishes itself from the sibling tool 'capture_screen' by specifying that this tool is for text assertions while capture_screen is for visual aspects.

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

Usage Guidelines5/5

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

The description explicitly states when to use this tool: 'Use this instead of capture_screen to assert a value' and explains why capture_screen is not suitable for assertions (7KB chunks, JPEG compression). It also specifies when capture_screen remains appropriate: 'capture_screen remains the tool for anything visual -- z-order, overlap, a missing glyph.' This provides clear usage boundaries.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/TheRolists/gmod-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server