Skip to main content
Glama
dvcrn

Siri Shortcuts MCP Server

by dvcrn

open_shortcut

Quickly launch Siri Shortcuts on macOS by opening them directly in the Shortcuts app. Simplify workflow automation with dynamic shortcut access through the Siri Shortcuts MCP Server.

Instructions

Open a shortcut in the Shortcuts app

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesThe name of the shortcut to open

Implementation Reference

  • The handler function for the 'open_shortcut' tool. It executes the shell command 'shortcuts view <name>' to open the specified shortcut in the Shortcuts app, returning success or error.
    const openShortcut = async (params: OpenShortcutInput): Promise<ToolResult> => {
      return new Promise((resolve, reject) => {
        const command = `shortcuts view '${params.name}'`;
        exec(command, (error, stdout, stderr) => {
          if (error) {
            reject(
              new McpError(
                ErrorCode.InternalError,
                `Failed to open shortcut: ${error.message}`,
              ),
            );
            return;
          }
          if (stderr) {
            reject(
              new McpError(
                ErrorCode.InternalError,
                `Error opening shortcut: ${stderr}`,
              ),
            );
            return;
          }
          resolve({ success: true, message: `Opened shortcut: ${params.name}` });
        });
      });
    };
  • Zod schema defining the input for the open_shortcut tool: an object with a required 'name' string.
    const OpenShortcutSchema = z
      .object({
        name: z.string().describe("The name of the shortcut to open"),
      })
      .strict();
  • shortcuts.ts:300-304 (registration)
    Registration of the 'open_shortcut' tool in the base tools array, specifying name, description, input schema, and run handler that delegates to openShortcut.
      name: ToolName.OPEN_SHORTCUT,
      description: "Open a shortcut in the Shortcuts app",
      inputSchema: zodToJsonSchema(OpenShortcutSchema) as ToolInput,
      run: (params: any) => openShortcut(params as OpenShortcutInput),
    },
  • shortcuts.ts:391-392 (registration)
    Dispatch logic in the CallToolRequest handler that invokes openShortcut when the tool name is OPEN_SHORTCUT.
    case ToolName.OPEN_SHORTCUT:
      result = await openShortcut(args as OpenShortcutInput);
  • ToolName enum value defining the string name 'open_shortcut'.
    OPEN_SHORTCUT = "open_shortcut",
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure but offers minimal information. It states the action but doesn't explain what 'opening' entails (does it launch the app? display details? require specific permissions?), whether it's read-only or has side effects, or what happens if the shortcut doesn't exist.

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?

The description is extremely concise - a single sentence that directly states the tool's purpose with zero wasted words. It's front-loaded and efficiently communicates the core functionality without unnecessary elaboration.

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 tool with no annotations, no output schema, and sibling tools that perform related but distinct operations, the description is insufficiently complete. It doesn't explain what 'opening' means operationally, how it differs from 'running', what the expected outcome is, or address potential error conditions.

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?

The schema description coverage is 100%, with the single parameter 'name' clearly documented in the schema. The description doesn't add any parameter-specific information beyond what's already in the structured data, so it meets the baseline for high schema coverage without compensating value.

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 action ('Open') and target resource ('a shortcut in the Shortcuts app'), making the purpose immediately understandable. However, it doesn't explicitly differentiate from sibling tools like 'run_shortcut' - both involve interacting with shortcuts but serve different purposes.

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?

The description provides no guidance on when to use this tool versus alternatives like 'run_shortcut' or 'list_shortcuts'. There's no mention of prerequisites, appropriate contexts, or what distinguishes 'opening' from 'running' a shortcut, leaving the agent with insufficient usage context.

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

Related 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/dvcrn/mcp-server-siri-shortcuts'

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