Skip to main content
Glama
dvcrn

Siri Shortcuts MCP Server

by dvcrn

list_shortcuts

Enable quick access by listing all available Siri shortcuts on macOS through the MCP Server, helping users identify and manage shortcuts efficiently.

Instructions

List all available Siri shortcuts

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler function that lists all available Siri shortcuts by executing 'shortcuts list --show-identifiers', parsing the output, populating shortcut maps, and returning the list.
    const listShortcuts = async (): Promise<ToolResult> => {
      return new Promise((resolve, reject) => {
        exec("shortcuts list --show-identifiers", (error, stdout, stderr) => {
          if (error) {
            reject(
              new McpError(
                ErrorCode.InternalError,
                `Failed to list shortcuts: ${error.message}`,
              ),
            );
            return;
          }
          if (stderr) {
            reject(
              new McpError(
                ErrorCode.InternalError,
                `Error listing shortcuts: ${stderr}`,
              ),
            );
            return;
          }
          
          // Parse output with identifiers format: "Name (UUID)"
          const shortcuts = stdout
            .split("\n")
            .filter((line) => line.trim())
            .map((line) => {
              const trimmed = line.trim();
              // Extract name and identifier if present
              const match = trimmed.match(/^(.+?)\s*\(([A-F0-9-]+)\)$/);
              if (match) {
                return { 
                  name: match[1].trim(),
                  identifier: match[2]
                };
              }
              return { name: trimmed };
            });
    
          // Update the shortcut map with unique sanitized names
          const existingSanitizedNames = new Set<string>();
          shortcuts.forEach((shortcut) => {
            const uniqueSanitizedName = generateUniqueSanitizedName(shortcut.name, existingSanitizedNames);
            shortcutMap.set(shortcut.name, uniqueSanitizedName);
            existingSanitizedNames.add(uniqueSanitizedName);
            
            // Store identifier if present
            if ('identifier' in shortcut && shortcut.identifier) {
              shortcutIdentifierMap.set(shortcut.name, shortcut.identifier);
            }
          });
          resolve({ shortcuts });
        });
      });
    };
  • Input schema for list_shortcuts tool (empty object since no parameters required).
    const ListShortcutsSchema = z.object({}).strict();
  • shortcuts.ts:294-298 (registration)
    Registration of the list_shortcuts tool in the base tools array returned by getBaseTools().
      name: ToolName.LIST_SHORTCUTS,
      description: "List all available Siri shortcuts",
      inputSchema: zodToJsonSchema(ListShortcutsSchema) as ToolInput,
      run: listShortcuts,
    },
  • Enum defining the tool name constant LIST_SHORTCUTS = "list_shortcuts" used in registration and dispatching.
    enum ToolName {
      LIST_SHORTCUTS = "list_shortcuts",
      OPEN_SHORTCUT = "open_shortcut",
      RUN_SHORTCUT = "run_shortcut",
    }
  • shortcuts.ts:388-389 (registration)
    Dispatch/execution case in the CallToolRequest handler switch statement.
    case ToolName.LIST_SHORTCUTS:
      result = await listShortcuts();
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. It states the action 'List all available Siri shortcuts' but doesn't describe what 'available' means, whether it requires permissions, how results are returned, or any rate limits. For a tool with zero annotation coverage, this leaves significant behavioral gaps.

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 a single, efficient sentence with zero waste: 'List all available Siri shortcuts.' It's front-loaded with the core action and resource, making it immediately understandable. No extraneous information or structural issues are present.

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's simplicity (0 parameters, no output schema, no annotations), the description is incomplete. It doesn't explain what 'available' means, how results are structured, or any behavioral constraints. For a listing tool with no structured support, more context about output format or scope would be needed for adequate completeness.

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

Parameters4/5

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

The tool has 0 parameters with 100% schema description coverage, so the schema fully documents the absence of inputs. The description doesn't need to compensate for parameter documentation, and it appropriately doesn't mention parameters. Baseline for 0 parameters is 4, as it avoids unnecessary parameter discussion.

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 verb 'List' and the resource 'Siri shortcuts' with the qualifier 'all available', making the purpose unambiguous. It distinguishes from siblings open_shortcut and run_shortcut by focusing on listing rather than execution. However, it doesn't specify output format or scope beyond 'available', leaving minor room for improvement.

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 explicit guidance is provided on when to use this tool versus alternatives like open_shortcut or run_shortcut. The description implies it's for listing shortcuts, but doesn't clarify prerequisites, context, or exclusions. Usage is implied rather than explicitly stated, which could lead to confusion in tool selection.

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