Skip to main content
Glama
segalz

mcp-computer-use

by segalz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

look_at_screen

Ask one short question about what a computer window shows and get a concise JSON answer, including summary, confidence, and details. Read-only and token-efficient.

Instructions

Ask ONE short English question about what a window on this computer shows; get short JSON back (windows_seen, status, summary, confidence, details, model_used, duration_seconds, memory_mb). details is filled by code: project, session, branch, next_step, failures, files, background_tasks when found. Read-only: never clicks or types. Pass app when known. For multi-part checks call step by step (status first, then details). On error, follow error.suggestion. client and session_id are OPTIONAL. Without them every call is independent: the full screen is re-read, no 'what changed' is possible and no file is written. With them the server keeps context between calls (more accurate, shorter answers, plus changed_since_last). Reuse the same pair for one task; sending a new session_id replaces the old one for that client. keep_warm (optional bool) keeps the model loaded 10 min instead of 3 when you will ask again soon. Call release_model() when your task is done.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
appNoOptional app/window name, e.g. 'Claude' or 'ChatGPT'. Pass it when known.
clientNoOptional. Your client name, e.g. 'codex' or 'claude' ([A-Za-z0-9_-], max 64). Used with session_id to keep context between calls.
questionYesOne short, focused question in English (max 300 chars), e.g. 'Is Claude working or finished?'. Split bigger checks into several calls.
keep_warmNoOptional. true = keep the model loaded 10 min (session value) instead of 3 min, when you will ask again soon without a session_id.
session_idNoOptional. A session name you choose, e.g. 'fix-ui' ([A-Za-z0-9_-], max 64). Reuse it on every call of the same task to get context and 'changed_since_last'. A new value replaces your previous session. Omit it and each call is independent (full re-read, no file).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.8/5.0
Behavior5/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 discloses read-only behavior (never clicks or types), the effect of omitting client/session_id (full re-read, no 'what changed', no file written), the effect of providing them (context, changed_since_last, file written), session replacement semantics, and the keep_warm timeouts. That is rich behavioral context beyond the schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is dense and front-loaded with the primary action, then output fields, then behavioral rules. It is slightly long and the session/client paragraph could be tightened, but every sentence earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 5-param tool with no output schema and no annotations, the description covers return fields, read-only safety, session behavior, error handling, and cleanup via release_model. An agent has everything needed to call it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is already 100%, so the baseline is 3. The description still adds value by linking session_id and client to outcomes (context, changed_since_last, full re-read without them) and explaining keep_warm's 10-min vs 3-min load, plus the step-by-step pattern for app filtering. It doesn't add syntax details that the schema lacks, so it falls short of 5.

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 states a specific verb and resource: ask one short question about what a window shows, and returns JSON with named fields. Siblings (ping, health, release_model) are clearly different operations, so differentiation is implicit but obvious.

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?

Explicit guidance: pass `app` when known, for multi-part checks call step by step with status first then details, follow error.suggestion on error, and call release_model() when done. It names when to reuse sessions and when to omit them. Nothing is left to inference about when to use this tool.

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