Skip to main content
Glama
Sign In
control-expert-mcp

control-expert-mcp

by apexsotjo-blip
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

show_ui

Show, maximize, minimize, or restore the Control Expert window to enable human supervision or manual control of the automation session.

Instructions

Make the Control Expert window of this automation session visible so a human can watch or take over. state: show_normal, show_maximized, minimize, restore.

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

Input Schema

NameRequiredDescriptionDefault
stateNoshow_normal

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations, the description discloses the action and possible states. However, it omits details about side effects (e.g., focusing, error conditions) or that it's non-destructive. Still adequate for a simple UI action.

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: first specifies the action and purpose, second enumerates states. No wasted words, front-loaded with key information.

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?

For a simple tool with one optional parameter and no output schema, the description covers purpose and parameter values. Lacks mention of behavior when already visible or error handling, but is largely sufficient.

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?

The schema has 0% description coverage, leaving the parameter 'state' undocumented. The description fully compensates by listing the four valid values (show_normal, show_maximized, minimize, restore), adding essential meaning.

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?

Clearly states the verb 'Make visible' and the resource 'Control Expert window', distinctly differentiating from all sibling tools which focus on project and hardware operations.

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?

Explicitly states the purpose 'so a human can watch or take over', implying when to use, but lacks explicit when-not or alternative guidance. Since no other sibling provides UI visibility, absence of exclusions is acceptable.

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

Deploy Server

Other Tools