Skip to main content
Glama
linux-computer-use-mcp

linux-computer-use-mcp

by dhakseshr

hold_key

Press and hold a key or key combination for up to 10 seconds, then release it to perform sustained shortcuts or long-press actions.

Instructions

Hold a key or combo down for some seconds (max 10), then release.

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": {
      "keys": "<keys>",
      "seconds": "<seconds>"
    },
    "name": "hold_key"
  }
}

Input Schema

NameRequiredDescriptionDefault
keysYes
secondsYes
screenshotNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

B3.3/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, and it does disclose two useful traits: a hard max of 10 seconds and the fact that the key is released automatically afterward. It says nothing about permissions, failure behavior, or that a screenshot is captured by default, leaving meaningful gaps for a mutation-style input tool.

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

Conciseness4/5

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

One compact sentence with the action and the duration bound front-loaded. No wasted wording, though it is arguably too terse given the undocumented parameters.

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

Completeness2/5

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

For a three-parameter tool with no annotations, no output schema, and 0% schema description coverage, the description leaves the screenshot parameter and the key-string format entirely unexplained. An agent can guess the core call but cannot know what a screenshot flag does here.

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 description coverage is 0%, so the description must compensate, and it partially does: 'key or combo' hints at the keys format and 'max 10' adds a constraint absent from the schema. However, the accepted key/combo syntax is never specified and the screenshot parameter is not mentioned at all.

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?

States a specific verb pair and resource: 'Hold a key or combo down for some seconds... then release.' The hold-and-release semantics implicitly separate it from press_key, which the agent can infer from the duration language, though no sibling is named explicitly.

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?

Usage is only implied by the mechanics — you use it when you need a key held for a duration. There is no explicit statement of when to prefer this over press_key, no prerequisites, and no exclusions.

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