Skip to main content
Glama
Sign In
Raycast MCP Server

Raycast MCP Server

by ExpertVagabond
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

raycast_search

Search and launch applications, files, or commands via Raycast, with an option to execute the first result automatically.

Instructions

Search and launch applications, files, or commands via Raycast

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "raycast_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesSearch query for Raycast
executeNoExecute the first result automatically

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3.2/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 burden of behavioral disclosure. It does not describe side effects, whether launching is destructive, what permissions are needed, or what happens when execute is true. The description only restates the basic action without adding behavioral context.

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 that is front-loaded with the core action and resource. It contains no unnecessary words and is appropriately sized.

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 that can launch applications and execute commands, the description is incomplete without annotations or output schema. It fails to describe side effects, prerequisites, or potential risks, leaving significant gaps for an agent to infer behavior.

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 schema already documents both parameters clearly. The description adds no additional meaning beyond what the schema provides, so the baseline score of 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 states a specific verb (Search and launch) and resource (applications, files, or commands) via Raycast. It clearly conveys the core purpose, though it does not explicitly differentiate itself from sibling tools like raycast_open, which might overlap in launching applications.

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?

The description implies usage for searching and launching, but provides no explicit guidance on when to use this tool versus alternatives such as raycast_open or raycast_shortcut. There are no exclusions or conditions mentioned.

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