Skip to main content
Glama
Sign In
computer-use-mac-mcp

computer-use-mac-mcp

by somethingforheheda
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

zoom

Capture a magnified screenshot around a selected screen coordinate to inspect details precisely. Use when you need a close-up view of a specific area.

Instructions

Take a zoomed-in screenshot of the area around the specified coordinate.

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": {
      "coordinate": "<coordinate>"
    },
    "name": "zoom"
  }
}

Input Schema

NameRequiredDescriptionDefault
coordinateYesCenter of zoom region [x, y]

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

With no annotations provided, the description carries the disclosure burden. It states the main behavior (capturing a zoomed image) but does not disclose whether the tool returns an image, whether it moves the viewport or cursor, or how the zoom scale is determined.

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 definition is a single, front-loaded sentence with no filler. Every word contributes to the agent's understanding of the action and its target.

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 tool with only one required parameter and no nested objects, the description plus the 100%-covered schema is nearly complete. It would be slightly more complete if it stated the expected result/return value or zoom behavior explicitly, but the phrase 'zoomed-in screenshot' already implies the output.

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 100% and the schema already explains the coordinate as the 'Center of zoom region [x, y]'. The description adds no extra semantic detail such as pixel/coordinate units or acceptable bounds, so it stays at the baseline for fully documented schemas.

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 uses a specific action verb ('Take a zoomed-in screenshot') and a clear resource ('area around the specified coordinate'). This distinguishes it from the sibling 'screenshot' tool by emphasizing the localized, zoomed scope.

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

Usage Guidelines4/5

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

The phrase 'zoomed-in screenshot ... around the specified coordinate' makes the targeted use case clear: local close-up inspection rather than a general screenshot. It does not explicitly name alternatives or list when-not-to-use conditions, so it falls just short of a 5.

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