Skip to main content
Glama

combo

Press multiple raw keys together as one chord to trigger shortcuts like cmd+tab in keyboard- or mouse-controlled apps.

Instructions

Press several raw keys together (e.g. ['cmd', 'tab']).

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>"
    },
    "name": "combo"
  }
}

Input Schema

NameRequiredDescriptionDefault
keysYes
hold_msNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden. 'together' hints at simultaneity, but it says nothing about whether keys are auto-released afterward, how the modifiers behave, whether the call blocks, or what errors occur if a key name is invalid — all critical for a synthetic-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.

Conciseness5/5

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

A single front-loaded sentence with an embedded example and no filler. Nothing could be removed without losing information.

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 synthetic-input tool with zero annotations, no output schema, and two undocumented parameters, one sentence is thin. An agent still lacks the hold duration meaning, release semantics, and failure modes needed to invoke it reliably.

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 0% and the array items are untyped, so the ['cmd','tab'] example is genuinely valuable — it establishes that keys are lowercase string names and that order may matter. However, the second parameter hold_ms (default 120) is never explained, so half the surface remains undocumented in both schema and description.

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 ('Press') plus the resource ('several raw keys together') and gives a concrete example combo ['cmd','tab'], which makes the multi-key simultaneous behavior unambiguous. It stops short of naming sibling tools such as press or key_tap, so differentiation has to be inferred from 'together'.

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 implied: call this when multiple keys must go down at once rather than one key (press/key_tap) or separate down/up calls (key_down/key_up). There is no explicit when-to-use/when-not statement, no mention of alternatives, and no note about focus or which app receives the input.

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