Skip to main content
Glama
Sign In
Copilot Desktop MCP

Copilot Desktop MCP

by avianhermana
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Take Screen Snapshot

take_screen_snapshot
Read-only

Capture a PNG snapshot of the active window or entire virtual desktop for visual inspection and OCR workflows.

Instructions

Capture a visual snapshot of the desktop or the currently active window and save as PNG. target can be 'active' (active window only) or 'screen' (entire virtual desktop).

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

Input Schema

NameRequiredDescriptionDefault
targetNoactive
output_pathNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior3/5

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

readOnlyHint=true is consistent with a capture operation, and the description usefully adds the file format and the meaning of the two capture modes. However, it never says where the PNG lands when output_path is left empty, whether files are overwritten, or that a filesystem artifact is created despite the read-only hint.

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, the core action front-loaded, and the target semantics immediately after. No filler words and no redundancy with the title.

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?

The returned value is covered by the output schema and the read-only safety profile by annotations, so those gaps don't count. What's still missing is the destination/overwrite behavior for output_path — a meaningful omission for a tool whose whole purpose is writing an image file.

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 description coverage is 0%, so the description carries the burden; it compensates well for `target` by spelling out the 'active' and 'screen' values that the schema leaves as an unconstrained string. It says nothing at all about `output_path` (its default of empty string, expected format, or destination), leaving one of two parameters unexplained.

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 uses a specific verb+resource ("capture a visual snapshot") and states the output medium (PNG) plus the two scopes (desktop vs active window). It is immediately clear what the tool produces, though it does not differentiate itself from nearby tools like get_active_window or list_open_windows.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: the target enumeration hints that you pick 'active' for a single window and 'screen' for the full desktop, but there is no explicit when-to-use statement, no when-not-to-use, and no named alternative for cases like enumerating windows instead of imaging them.

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