Skip to main content
Glama
Sign In
twiddle-mcp

twiddle-mcp

by roti-c137
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

screenshot

Capture a PNG screenshot for visual checks of colors, images, and layout. Use as a fallback when text or structure verification is insufficient.

Instructions

PNG screenshot — the fallback for purely visual checks (colors, images, layout polish). For text/structure, prefer get_ui_tree or wait_for: cheaper and more precise.

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

Input Schema

NameRequiredDescriptionDefault
deviceNoDevice id from list_devices. Optional when exactly one device is booted.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A4.2/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It mentions 'PNG screenshot' implying non-destructive read-only operation, but does not disclose details like resolution, format specifics, or potential delays. Adequate but minimal.

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, zero wasted words. Efficiently conveys purpose, usage guidance, and alternatives.

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's simplicity (one optional parameter, no output schema, no annotations), the description is reasonably complete. It explains what it does, when to use it, and suggests alternatives. Could mention output format or typical use case more explicitly, but largely sufficient.

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?

The description adds no information beyond the schema; the schema already has 100% coverage with a clear description for the optional 'device' parameter. Baseline 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 produces a PNG screenshot for visual checks, specifying its use case (colors, images, layout polish) and distinguishing it from sibling tools (get_ui_tree, wait_for) that are for text/structure.

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 advises using this tool for visual checks and preferring alternatives for text/structure, providing clear when-to-use and when-not-to-use guidance.

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