Skip to main content
Glama

run_shortcut

Executes a macOS Shortcut by its exact name only when explicitly requested, enabling on-device automation through Apple Bridge MCP.

Instructions

Run a shortcut by exact name. Only call when the user explicitly asks to run a shortcut.

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

Input Schema

NameRequiredDescriptionDefault
nameYesExact shortcut name

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden, and it says nothing about what executing a shortcut does, whether it mutates state, what permissions or confirmations are needed, or how an unknown name is handled. For an execution tool with open-ended side effects, that is a substantial omission.

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?

Two short sentences, action first, constraint second, with no filler. Every clause carries information an agent needs.

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

Completeness3/5

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

For a one-parameter tool with full schema coverage, the definition covers invocation adequately. However, with no annotations and no output schema, an agent still cannot tell what the shortcut returns, whether it is safe to retry, or what a failed name match looks like.

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% and the single parameter is documented as "Exact shortcut name"; the description's "by exact name" reinforces case/string exactness but adds no format examples or fallback behavior. Baseline 3 applies since the schema already does the work.

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 and resource ("Run a shortcut") and narrows the input to an exact name, which is enough to distinguish it from siblings like list_shortcuts or create_note. It stops short of naming any sibling explicitly, so the differentiation is inferred rather than stated.

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

Usage Guidelines4/5

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

"Only call when the user explicitly asks to run a shortcut" is a clear, enforceable when-to-use gate that suppresses speculative invocation. It does not mention the complementary flow of listing shortcuts to resolve an exact name, but the guidance it does give is unambiguous.

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