Skip to main content
Glama
Sign In
OmniCommanderMCP

OmniCommanderMCP

by kaannsaydamm
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

capture_screen_image

Take a screenshot of the primary display and return it as a PNG image.

Instructions

Capture the primary screen and return a directly viewable PNG image.

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

Input Schema

NameRequiredDescriptionDefault
pathNo./omni-screen.png

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.6/5.0
Behavior2/5

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

The description mentions a 'directly viewable PNG image' but does not disclose behavioral details such as permission requirements, whether it is blocking, or what happens if the path parameter is omitted. No annotations are present to fill this gap.

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

Conciseness3/5

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

The description is a single sentence, which is concise, but it lacks important details. It is appropriately short but not fully effective.

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?

Given the tool has one optional parameter and no output schema, the description is partially complete. It states the output format but does not explain parameter behavior or return value structure, which is adequate but not thorough.

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

Parameters1/5

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

The description does not explain the 'path' parameter at all, despite 0% schema coverage. The schema shows a default value, but the description adds no semantic meaning beyond what the schema provides.

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 clearly states the tool captures the primary screen and returns a PNG image. However, it does not distinguish from the sibling tool 'capture_screen', which may have similar functionality.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives like 'capture_screen'. The description does not include any context for usage.

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