Skip to main content
Glama

owa_screenshot

Capture what is on the app window or a presentation screen to diagnose layout, colour or unnameable on-screen issues when text output falls short. Reads only; changes nothing.

Instructions

A picture of what the operator is looking at right now: the app window, or a projector screen by id. Use it when the words are not enough -- a layout that looks wrong, a colour, something on screen the user cannot name. It READS the window and changes nothing, so nothing appears in their way. Prefer owa_app_state, owa_list_screens and owa_list_ui first: they answer most questions in a fraction of the tokens a picture costs.

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

Input Schema

NameRequiredDescriptionDefault
pageNo
screenIdNoA showing presentation screen instead of the app window. Fails when that screen is not showing, which is itself the answer to most questions about it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2026.11.15

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it declares the operation READS the window and changes nothing, so nothing appears in the user's way, and it flags the token cost. It does not describe the output form (image dimensions, format) or timing/failure behaviour beyond what the schema says about a non-showing screen.

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 front-loaded with the core definition, then the usage cue, then the routing advice, with no filler sentences. The phrasing is slightly conversational but each clause adds a decision-relevant fact.

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

Completeness3/5

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

For a two-parameter read tool with no annotations and no output schema, the description covers safety, cost and alternatives well. Gaps remain: the page parameter is unexplained and there is no hint about what the returned picture looks like, which matters for a screenshot tool.

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 coverage is 50%: screenId has its own description including the failure mode when that screen is not showing, and the prose reinforces that it means a presentation screen rather than the app window. The page parameter is undocumented in both schema and description, so the prose does not compensate for the coverage gap but does add real meaning for the one documented parameter.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a concrete resource and scope: a picture of the app window or a named projector screen by id. It clearly separates itself from owa_app_state, owa_list_screens and owa_list_ui, but never mentions the sibling take_screenshot, so an agent cannot tell those two apart from this definition alone.

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?

It gives both sides of the routing decision: use this when words are insufficient (wrong layout, colour, unnamed on-screen element), and prefer owa_app_state, owa_list_screens and owa_list_ui first because they are far cheaper in tokens. That is explicit when-to-use, when-not-to-use, and named alternatives.

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