Skip to main content
Glama
Sign In
Raycast MCP Server

Raycast MCP Server

by ExpertVagabond
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

raycast_shortcut

Trigger predefined Raycast shortcuts or custom keyboard hotkeys to launch actions like clipboard history, emoji, calculator, screenshot, and timers.

Instructions

Trigger Raycast shortcuts and hotkeys

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": "raycast_shortcut"
  }
}

Input Schema

NameRequiredDescriptionDefault
shortcutNoPredefined Raycast shortcut to trigger
custom_keyNoCustom keyboard shortcut (e.g., "cmd+shift+c")

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

C2.9/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 behavioral burden. It does not say whether Raycast must be running, whether permissions are needed, or what side effects (screenshot, timer, calculator) the shortcuts produce – all relevant for an action-triggering tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no filler. It is efficient, though arguably under-specified rather than ideally concise for an action tool.

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?

With no annotations, no output schema, and no behavioral detail, the definition is thin for a tool that fires UI actions. It never explains what happens on success/failure, whether shortcuts conflict, or what the enum entries actually do.

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 description coverage is 100%, so the enum values and the custom_key format example are already documented in the schema. The description adds nothing about how the two parameters interact (e.g., precedence when both shortcut and custom_key are supplied), so the baseline 3 is appropriate.

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 gives a specific verb ('Trigger') and resource ('Raycast shortcuts and hotkeys'), making the action unambiguous. It stops short of differentiating itself from siblings like raycast_open or raycast_window, which also act on the Raycast UI.

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?

There is no guidance on when to use this rather than raycast_open, raycast_window, or the other Raycast siblings. No exclusions, prerequisites, or conditions are stated, leaving the agent to guess from the name alone.

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

Deploy Server

Other Tools