Skip to main content
Glama

finder_search

Search files on your Mac using Spotlight to locate documents, applications, and folders. Query by name or content to retrieve specific file paths.

Instructions

Search files using Spotlight

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • server.js:58-58 (registration)
    Tool name 'finder_search' is defined in the TOOLS array with description 'Search files using Spotlight'
    ["finder_search", "Search files using Spotlight"],
  • server.js:82-86 (registration)
    Tool is registered with the MCP server using a generic loop that creates stub handlers for all tools
    for (const [name, desc] of TOOLS) {
      server.tool(name, desc, {}, async () => ({
        content: [{ type: "text", text: "This is an inspection stub. Install Pilot MCP on macOS: npx -y local-mcp@latest setup" }],
      }));
    }
  • server.js:82-86 (handler)
    Stub handler for finder_search - returns static message indicating this is an inspection stub. Real implementation is in native macOS binary.
    for (const [name, desc] of TOOLS) {
      server.tool(name, desc, {}, async () => ({
        content: [{ type: "text", text: "This is an inspection stub. Install Pilot MCP on macOS: npx -y local-mcp@latest setup" }],
      }));
    }
Behavior2/5

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

No annotations provided, so description carries full burden. Mentions 'Spotlight' implying macOS indexing, but fails to disclose search scope (filename vs content), result format/limits, case sensitivity, or permission requirements.

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?

Extremely terse at four words with zero redundancy. Every word conveys essential information, though the extreme brevity contributes to under-specification in other dimensions.

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?

Critically inadequate for a search tool. With no parameters, no output schema, and no annotations, the description must explain how to specify search criteria and what gets returned. It provides neither, leaving the agent unable to use the tool effectively.

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?

Input schema contains zero parameters (empty properties object). Per scoring rules, zero parameters establishes a baseline of 4. Description neither adds nor subtracts value regarding parameters.

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?

States specific action (search) and resource (files) with implementation detail (Spotlight). However, it fails to distinguish from sibling 'finder_list' or clarify scope differences from cloud storage searches like 'onedrive_search_files'.

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?

Provides no guidance on when to use this versus 'finder_list' (directory listing vs content search) or versus cloud storage search tools. No mention of prerequisites like Spotlight indexing being enabled.

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/lanchuske/local-mcp-releases'

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