pyside6-mcp

Overview Schema Source Related Servers Discussions Admin

get_widget_info

Inspect a widget's detailed properties and current state—geometry, text, visibility, enabled status, and dynamic Qt properties—to debug or verify UI behavior in PySide6 applications.

Instructions

Get detailed properties and state of a specific widget. Includes geometry, text, enabled/visible state, and dynamic Qt properties.

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": {
      "widget_id": "<widget_id>"
    },
    "name": "get_widget_info"
  }
}

Input Schema

Name	Required	Description	Default
`pid`	No	App pid from launch_app. Omit to target the last launched app. Required only when several apps are running and you need a specific one.
`widget_id`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 5, 2026

TDQS

A3.6/5.0

Behavior3/5

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

There are no annotations, so the description carries the full behavioral burden. It does disclose the kind of information returned and mentions dynamic Qt properties, which is useful. However, it does not explicitly state read-only behavior, failure behavior for unknown widgets, or prerequisites like a running app.

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 concise sentences with the main operation front-loaded and no filler. Every sentence adds relevant information about the tool's purpose or output scope.

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?

The tool is simple and output schema exists, so return-value detail is not required. Still, the description omits usage boundaries relative to many sibling tools and does not mention that widget_id likely comes from find_widget or get_widget_tree, leaving some ambiguity for an agent selecting among 21 tools.

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 only 50%; pid is described but widget_id is not. The description adds no parameter-specific guidance and does not explain how to obtain or format widget_id, so it fails to compensate for the schema gap.

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 a specific verb-resource pair: 'Get detailed properties and state of a specific widget.' It also enumerates content areas (geometry, text, enabled/visible state, dynamic Qt properties), which clearly distinguishes it from siblings like get_widget_tree or find_widget.

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 phrase 'specific widget' implies this tool is for inspecting one widget after its ID is known, but there is no explicit when-to-use guidance or comparison to alternatives. It does not direct the agent to find_widget for lookup or get_widget_tree for hierarchy.

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