Skip to main content
Glama
recursechat

Apple Shortcuts Server

by recursechat

list_shortcuts

Discover available shortcuts to automate tasks on Apple devices. This tool provides a complete list of shortcuts for users to browse and select automation options.

Instructions

List all available shortcuts

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function for the 'list_shortcuts' tool, which updates the list of shortcuts and returns them as a text response.
    case "list_shortcuts": {
      updateShortcutsList();
      console.error("MCP shortcuts: Listing shortcuts");
      return {
        content: [
          {
            type: "text",
            text: `Available shortcuts:\n${availableShortcuts.join("\n")}`,
          },
        ],
        isError: false,
      };
    }
  • Schema definition for the 'list_shortcuts' tool, specifying no input parameters.
    {
      name: "list_shortcuts",
      description: "List all available shortcuts",
      inputSchema: {
        type: "object",
        properties: {},
      },
    },
  • src/index.ts:164-166 (registration)
    Registers the tool list handler, which exposes the 'list_shortcuts' tool via the TOOLS array.
    server.setRequestHandler(ListToolsRequestSchema, async () => ({
      tools: TOOLS,
    }));
  • src/index.ts:168-170 (registration)
    Registers the general tool call handler that dispatches to specific tool handlers including 'list_shortcuts'.
    server.setRequestHandler(CallToolRequestSchema, async (request) =>
      handleToolCall(request.params.name, request.params.arguments ?? {})
    );
  • Helper function to fetch and parse the list of available shortcuts using the 'shortcuts list' command.
    function updateShortcutsList() {
      try {
        const stdout = execSync("shortcuts list").toString();
        availableShortcuts = stdout
          .split("\n")
          .map((line) => line.trim())
          .filter((line) => line.length > 0);
      } catch (error) {
        console.error("Failed to list shortcuts:", error);
        availableShortcuts = [];
      }
    }
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states the basic function without mentioning any behavioral traits like whether the list is paginated, sorted, filtered, or if there are rate limits, authentication requirements, or side effects. This leaves significant gaps for a tool with zero annotation coverage.

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 no wasted words. It's appropriately sized for a simple tool and front-loads the essential information. Every word earns its place in conveying the core purpose.

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), the description is minimal but incomplete. It lacks context about the return format (e.g., what data is included in the list), behavioral details, or usage guidelines. While the tool is straightforward, the description doesn't provide enough information for an agent to fully understand its operation without annotations.

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, and the schema description coverage is 100% (though empty). The description doesn't need to add parameter semantics, so it meets the baseline expectation for a parameterless tool. No additional value is needed or provided beyond the schema.

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 ('List') and resource ('all available shortcuts'), providing a specific verb+resource combination. However, it doesn't differentiate from its sibling 'run_shortcut' beyond the obvious difference between listing and executing, which keeps it from a perfect score.

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. There's no mention of prerequisites, context for usage, or comparison with the sibling 'run_shortcut' tool. It merely states what the tool does without indicating appropriate scenarios.

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

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/recursechat/mcp-server-apple-shortcuts'

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