Skip to main content
Glama

vnc_command

Control a remote desktop via VNC: send mouse clicks, keyboard input, take screenshots, and automate GUI interactions.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYesThe action to perform
xNoX coordinate
yNoY coordinate
toXNoDrag target X
toYNoDrag target Y
dxNoRelative X offset (nudge)
dyNoRelative Y offset (nudge)
buttonNoMouse button
keyNoKey name or combo string (e.g. "cmd+c")
keysNoArray of key names for combo (e.g. ["cmd","shift","3"])
textNoText to type or paste
directionNoScroll direction
amountNoScroll amount (default 3)
msNoWait duration in ms (default 500)
resetNoReset all params to defaults
max_dimensionNoMax screenshot dimension
cursor_crop_radiusNoCursor crop radius
click_hold_msNoClick hold duration
double_click_gap_msNoDouble-click gap
hover_settle_msNoHover settle wait
drag_position_msNoPre-drag position wait
drag_press_msNoDrag press hold
drag_step_msNoBetween interpolation pts
drag_settle_msNoSettle before release
drag_pixels_per_stepNoPoint density per pixel
drag_min_stepsNoMin interpolation steps
scroll_press_msNoScroll press-release gap
scroll_tick_msNoInter-tick delay
key_hold_msNoKey hold duration
combo_mod_msNoModifier settle delay
type_key_msNoKey hold during typing
type_inter_key_msNoInter-character delay
type_shift_msNoShift key settle
paste_settle_msNoPost-clipboard write wait
Behavior1/5

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

Tool has no description.

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

Conciseness1/5

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

Tool has no description.

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

Completeness1/5

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

Tool has no description.

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?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

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

Usage Guidelines1/5

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

Tool has no description.

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/ARAS-Workspace/claude-kvm'

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