Skip to main content
Glama
Corvus400

video-capture-mcp

by Corvus400
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

move_pointer

Move the macOS pointer to specified x and y coordinates without clicking. Prevents mouse-up events for hover-only desktop checks.

Instructions

Move the macOS pointer to one coordinate without clicking.

Requires macOS Accessibility permission for the launcher process. Use this
for single-point hover-only desktop checks when Computer Use drag would send
a mouse-up event and might activate the target.

For multiple hover/unhover points, prefer hover_sequence because it can
activate an app_name first and interpolate movement across segments.
The response echoes the final x and y coordinates.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
xYesmacOS screen x in points (logical pixels), origin = top-left of primary display.
yYesmacOS screen y in points (logical pixels), origin = top-left of primary display.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Tool Definition Quality

A4.5/5.0
Behavior4/5

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

No annotations, so description covers key behaviors: requires Accessibility permission, no clicking, returns coordinates. Could add more on error handling but sufficient.

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?

Three concise sentences, front-loaded with action, no wasted words.

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

Completeness5/5

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

For a simple two-param tool with output schema, description covers purpose, usage, requirements, and return value. Complete.

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% with clear descriptions. Description adds context about hover-only purpose but doesn't repeat parameter details. Baseline 3 is appropriate.

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?

Description clearly states it moves macOS pointer without clicking, distinguishes from hover_sequence by noting single-point vs multiple points. Verb+resource is specific.

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?

Explicitly mentions when to use (single-point hover-only desktop checks) and when not (multiple points prefer hover_sequence). Also notes alternative tool by name.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Corvus400/video-capture-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server