Skip to main content
Glama
Sign In
macos-agent-bridge

macos-agent-bridge

by juliusloon
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

finder_search_files

Read-onlyIdempotent

Search filenames recursively within authorized macOS file roots to locate files by case-insensitive filename substring, without accessing private search indexes.

Instructions

Search filenames recursively within authorized root, at most 10,000 visited entries. Does not access Raycast private search index. [v1.0.0; permissions: none]

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": {
      "path": "<path>",
      "query": "<query>"
    },
    "name": "finder_search_files"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesAbsolute path within user-authorized file roots
limitNo
queryYesCase-insensitive filename substring

Output Schema

NameRequiredDescriptionDefault
dataYes
toolYestool name
errorYes
statusYes
versionYessemantic version

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, non-open-world behavior, so the safety profile is covered. The description adds genuinely new behavioral facts beyond them: a 10,000-visited-entry traversal cap, the fact it avoids the private search index, and an explicit 'permissions: none' claim.

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?

Three compact sentences with the core action front-loaded, followed by the scope exclusion and metadata tag. Little waste; the version/permissions tag is arguably extraneous but small.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need no explanation, and annotations carry the safety profile. The description covers scope, traversal bound, and a permission note; the only real gap is the unstated semantics of the limit parameter.

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 coverage is 67%: path and query are documented in-schema, while limit has an empty description. The description reinforces that the query matches filenames, but it does not clarify the limit parameter or its distinction from the 10,000-entry traversal cap. Baseline 3 fits a schema doing most of the work.

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 a specific verb (search) and resource (filenames) with a scope qualifier ('recursively within authorized root'), which implicitly separates it from directory-listing siblings like finder_list_files. It does not explicitly name a sibling alternative, so it falls just short of full differentiation.

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 recursion scope and 'does not access Raycast private search index' line imply when this tool applies versus other finders, but there is no explicit when-to-use/when-not guidance or named alternative (e.g. finder_list_files for non-recursive listing). Usage must be inferred.

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