Skip to main content
Glama

finder_search

Search files on your Mac using Spotlight to quickly locate documents, folders, and other items.

Instructions

Search files using Spotlight

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • server.js:61-61 (registration)
    Tool 'finder_search' is registered in the TOOLS array on line 61. It is registered with the description 'Search files using Spotlight' but has no meaningful implementation — it returns a stub message. The real implementation is in a native binary outside this codebase.
    ["finder_search", "Search files using Spotlight"],
  • The handler for all tools (including finder_search) is a stub — it returns a placeholder message telling the user to install the real 'local-mcp' binary via npx. The actual Spotlight search logic is implemented in a native binary (macOS/Windows/Linux) not present in this codebase.
    for (const [name, desc] of TOOLS) {
      server.tool(name, desc, {}, async () => ({
        content: [{ type: "text", text: "This is an inspection stub. Install Local MCP: npx -y local-mcp@latest setup" }],
      }));
    }
  • The schema for finder_search is an empty object '{}', meaning no input parameters are defined in this stub. The real tool likely has parameters in the native binary.
    server.tool(name, desc, {}, async () => ({
Behavior2/5

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

The description mentions the underlying engine (Spotlight) but does not disclose key behaviors: what is searched (indexed files only?), how queries are entered (since no parameters), return format, or performance characteristics. Without annotations, this gap is significant.

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?

Single sentence is concise and front-loaded. However, it omits critical information about usage, making it under-specified rather than 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?

The description does not explain how to use a search tool with no parameters. It is unclear how the agent should invoke it or what the output will be. A complete description would include details on specifying the search query and output format.

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 has 0 parameters, so description adds no parameter meaning, but baseline for 0 params is 4. No need to elaborate.

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 tool searches files using Spotlight, which is a specific verb-resource pair. It distinguishes from sibling tools like finder_list (list without search) and onedrive_search_files (remote files). However, it could be more precise about what type of search (filename, content).

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?

No guidance on when to use this tool versus alternatives like onedrive_search_files or searc_notes. The description does not mention prerequisites, limitations, or typical use cases.

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