Skip to main content
Glama
Sign In
macos-screen-mcp

macos-screen-mcp

by dla-kirito
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

preview_file

Open files for preview on macOS using default app, Chrome, or Quick Look. Supports HTML, images, PDFs, and more.

Instructions

Open a file for preview on macOS. Supports HTML (opens in Chrome), images, PDFs, and other files. Can use default app, Chrome, or Quick Look.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "file_path": "<file_path>"
    },
    "name": "preview_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
file_pathYesAbsolute or relative path to the file to preview
methodNoHow to open: default app, Chrome browser, or Quick Look. Default: browser for HTML, open for others

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.2

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It discloses that the tool opens a file for preview and offers three methods, which implies non-destructive behavior. However, it does not mention potential errors, return values, or platform dependency beyond macOS.

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?

The description is concise with two sentences, front-loading the core purpose. Every sentence adds value without redundancy or filler.

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?

For a simple tool with two parameters and no output schema, the description covers the main functionality (supported types, methods). It could be more complete by mentioning return behavior or error handling, but given the low complexity, it is adequate.

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 input schema covers 100% of parameters with descriptions. The description adds context about supported file types and method options, but these largely overlap with schema defaults. It does not introduce new meaning beyond the schema.

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's function with a specific verb ('Open') and resource ('file for preview on macOS'), and lists supported file types. It distinguishes from sibling tools like capture_screen and get_browser_content, which are clearly different actions.

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?

The description implies usage for previewing files and mentions supported types, but does not explicitly guide when to use this tool versus alternatives or when not to use it. No reference to siblings is made.

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