InfiAutomation MCP

Overview Schema Source Related Servers Discussions Admin

ui_windows

Read-only

Lists live web and Electron renderer windows with session-local IDs, titles, URLs, and selected state, so you can identify and target windows without opening tabs.

Instructions

List live web/Electron renderer windows with session-local IDs, titles, URLs and selected state. Does not open tabs. Native window trees are available through ui_snapshot.

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": {
      "sessionId": "<sessionId>"
    },
    "name": "ui_windows"
  }
}

Input Schema

Name	Required	Description	Default
`sessionId`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Addedv0.5.0Nov 5, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, and the description adds real context beyond them: IDs are session-local (ephemeral, not stable identifiers), and the tool does not create tabs. It says nothing about enumerating only 'live' windows in edge cases or ordering, but the added scoping is meaningful.

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 sentences, front-loaded with the verb and resource, then the return fields, then the exclusion and the alternative. Nothing is padding.

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?

With no output schema, the description does the work of naming returned fields (IDs, titles, URLs, selected state), and the read-only profile is covered by annotations. The main gap is that the sole required parameter is never explained, which matters for a tool that cannot be called without it.

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 0% for the single required sessionId, so the description should carry that burden; 'session-local IDs' only hints that the result is scoped to a session. It never states that sessionId identifies the session whose windows are listed or what happens with an invalid session.

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?

States a specific verb and resource ('List live web/Electron renderer windows') plus the returned fields, and explicitly separates itself from ui_snapshot for native window trees. An agent can pick this over siblings without opening the schema.

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?

Names the alternative (ui_snapshot) and the condition that selects it, and 'Does not open tabs' rules out a plausible misuse. It stops short of saying when to call this versus ui_window_select or how the listed windows feed later actions.

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