Skip to main content
Glama
Sign In
twiddle-mcp

twiddle-mcp

by roti-c137
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

wait_for_idle

Block until the UI stops changing after navigation, ignoring noisy elements like clocks and spinners, to ensure screen stability before reading.

Instructions

BLOCK until the UI stops changing (animations/loads settled). Volatile elements like clocks and spinners marked noisy are ignored. Use after navigation before reading the 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": "wait_for_idle"
  }
}

Input Schema

NameRequiredDescriptionDefault
deviceNoDevice id from list_devices. Optional when exactly one device is booted.
quietMsNoQuiet window, default 500ms
timeoutMsNoDefault 15000, max 120000

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A4/5.0
Behavior3/5

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

No annotations exist, so description must cover behavioral traits. It mentions blocking, ignoring noisy elements, and implied idleness detection. However, it does not disclose timeout behavior, error conditions, or whether the tool returns a status, leaving gaps for an agent.

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, no redundancy, front-loaded with key action and context. Every sentence adds value.

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 and three optional parameters, the description adequately explains purpose and usage. Lacks detail on return value or timeout handling, but overall sufficient for a blocking utility in context.

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 covers all three parameters with descriptions (100% coverage). The description adds no extra parameter-specific details, so baseline of 3 is appropriate.

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 clearly states the tool blocks until UI stops changing, using strong verb 'BLOCK' and specifying the resource. It distinguishes from sibling 'wait_for' by focusing on idleness rather than a specific condition, and adds detail about ignoring noisy elements.

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 advises use after navigation before reading the screen, providing clear context. Lacks explicit exclusions or alternatives, but the guidance is direct and actionable.

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