Skip to main content
Glama

list_shortcuts

Read-only

Lists the names of shortcuts in the Shortcuts app, either across all shortcuts or filtered to a specific folder.

Instructions

List the names of the shortcuts in the Shortcuts app, all or from one folder.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_shortcuts"
  }
}

Input Schema

NameRequiredDescriptionDefault
folderNoFolder name. Ignores case. Default: all shortcuts.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds that only shortcut names are returned (not full shortcut data) and that the folder filter is optional, but says nothing about ordering or behavior when a folder 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?

One sentence with zero waste, front-loading the verb and resource before the optional scoping clause.

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

Completeness4/5

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

For a simple, zero-required-parameter read tool with full schema coverage and annotations, the description covers what the agent needs: what is listed, what is returned, and the optional scope. Only ordering and empty-folder behavior are left unstated, which are minor.

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 folder parameter already documents case-insensitivity and the 'all shortcuts' default. The phrase 'all or from one folder' restates rather than extends the schema, so baseline 3 applies.

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?

A specific verb and resource: 'List the names of the shortcuts in the Shortcuts app.' It also states scope ('all or from one folder'). No sibling covers shortcuts, so differentiation isn't needed, keeping it just under a 5.

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

Usage Guidelines3/5

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

Usage is implied by the tool's scope (enumerate shortcuts, optionally scoped to one folder) but there is no explicit when-to-use/when-not guidance or mention of alternatives for the folder-based restriction.

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