Skip to main content
Glama

computer.shortcut

Save, run, and organize reusable action chains for Windows automation. Use shortcuts to execute multi-step tasks with isolated scopes and AI-assisted cleanup.

Instructions

由主 AI 显式保存、运行和整理动作链;本地脚本负责作用域隔离、聚类和清理。整理 AI 仅在 useAi=true 时调用。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keepNo
nameNoshortcut 名称,例如“切换资源包”。
applyNo
limitNo
scopeNo默认 single;cross 使用独立的有序窗口路径记忆。
useAiNoorganize 时明确设为 true 才调用共享 API key 的整理 AI。
actionYes
paramsNo模板参数;高层时间值默认使用秒并允许小数,例如 mywait: 0.3;仅 kbops.at 使用毫秒。
removeNo
windowNosingle 的窗口句柄;run/list 等操作使用。
actionsNo
aliasesNo
applyAiNoorganize 时明确设为 true 才应用整理 AI 返回的 proposal;默认只返回 proposal。
newNameNo
windowsNocross 的窗口别名到窗口句柄映射,例如 {browser:"123",explorer:"456"}。
confirm_tokenNo运行高风险 shortcut 时传回的一次性确认令牌。
maxOperationsNo
afterFingerprintNo
beforeFingerprintNo
Install Server

TDQS

C2.9/5.0
Behavior3/5

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

The description discloses behavioral details about local scripts handling scope isolation/clustering/cleanup and the conditional invocation of organizing AI (useAi=true). However, with no annotations, it fails to mention side effects, mutability, or return behavior, leaving significant gaps.

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?

The description is brief and front-loaded with the core purpose, consisting of two sentences with no extraneous content. However, it may be too terse for the tool's complexity.

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?

Given the tool has 19 parameters, no output schema, and no annotations, this minimal description is inadequate. It does not explain return values, preconditions, or the significance of different actions, leaving substantial gaps for an AI agent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 42%, and the description adds no parameter semantics. It does not explain the roles of key parameters like 'action', 'scope', or 'confirm_token', so it fails to compensate for the coverage gap.

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?

The description clearly states the tool saves, runs, and organizes action chains, with a specific verb and resource. It distinguishes the tool's general function but does not explicitly differentiate it from the sibling shortcut.run, so it misses full differentiation.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives. There is no mention of scenarios, exclusions, or comparisons to sibling tools like shortcut.run or computer.invoke.

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

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/Ethanout/computer-use-plus'

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