finder_list

List files and folders in any macOS Finder directory, enabling AI agents to browse local storage and view directory contents on your Mac.

Instructions

List files in a Finder directory

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Implementation Reference

server.js:57-57 (registration)
The finder_list tool is registered in the TOOLS array with its description. This is part of a list of all tools that the Pilot MCP server exposes for discovery.
```
["finder_list", "List files in a Finder directory"],
```
server.js:82-86 (handler)
The handler function for finder_list (shared by all tools in this stub server). It returns a placeholder message indicating this is an inspection stub and directs users to install the actual Pilot MCP on macOS.
```
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 (schema)

The schema for finder_list is an empty object {}, meaning this stub accepts no parameters. The actual implementation would likely accept parameters like directory path.

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" }],
  }));
}

Tool Definition Quality

C2.8/5.0

Behavior2/5

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

With no annotations provided, the description carries the full disclosure burden but fails to state whether hidden files are included, what metadata is returned, if Finder must be running, or whether the operation is read-only. Critical behavioral traits are absent.

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?

The description is a single, efficient sentence with no filler. However, it may be overly terse given the lack of parameters and output schema, as it leaves critical operational details unexplained.

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 with zero parameters, no annotations, and no output schema, the description should explain the target directory selection logic and return format. It provides neither, leaving agents without sufficient context to predict invocation results.

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?

The input schema contains zero parameters, establishing a baseline score of 4 per the evaluation rubric. There are no parameters requiring semantic clarification beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states the action (List files) and domain (Finder directory), but given the tool accepts zero parameters, it critically omits WHICH directory is listed (e.g., current window, home directory, or default path). This ambiguity prevents clear differentiation from sibling `finder_search` and leaves invocation scope undefined.

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 provided on when to use this versus `finder_search` (for filtering) or `onedrive_list_files` (for cloud storage). The description purely states functionality without contextual selection criteria.

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

Install Server

Pilot MCP

finder_list

Instructions

Input Schema

Implementation Reference

Tool Definition Quality

Other Tools

Latest Blog Posts

MCP directory API