BCD — Bridge Control Delegate

search_files

Read-only

Find files and folders by name: case-insensitive substring of the name, or a glob on the whole name when query has * or ? (e.g. *.js, report-??.pdf), searched under path (default the work session workspace, or ~ without a session). Returns a JSON array of full paths (maxResults, default 100). Stops after 8 seconds; on macOS a folder too large to scan in time is answered from the Spotlight index, elsewhere with the results found so far and scanComplete false, so give the most specific folder you can.

Input Schema

TableJSON Schema

Name	Required	Description
`path`	No
`query`	Yes
`deviceId`	No	Computer name or id from list_devices. Optional with one computer online or a default set.
`maxResults`	No
`workSessionId`	No	Work session from create_work_session. Pass the same ID on every call in this conversation; omit for legacy unscoped work.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 30, 2026

removedInput schema / properties / path / default
```
Removed value: -"~"
```

addedInput schema / properties / workSessionId

Added value: +{
+  "description": "Work session from create_work_session. Pass the same ID on every call in this conversation; omit for legacy unscoped work.",
+  "format": "uuid",
+  "type": "string"
+}

First observedSep 30, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Goes well beyond the readOnly/openWorld annotations: discloses the 8-second scan deadline, the macOS Spotlight index fallback, the truncated-result behavior with scanComplete false elsewhere, and the maxResults cap. These operational quirks are exactly what an agent needs to interpret partial results.

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?

Front-loads the core operation and matching rules, then handles return value, timeout, and the specificity tip in order of importance. Dense but every clause carries information; the final sentence is long but justified by the fallback nuance.

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

Completeness5/5

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

Despite no output schema, the description specifies the return shape (JSON array of full paths) and the truncation/scanComplete semantics. Combined with the parameter coverage, an agent has everything needed to call and interpret this tool correctly.

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?

Schema coverage is only 40%, so the description must compensate — and it does for query (substring vs glob syntax with examples), path (default resolution), and maxResults (default 100). The remaining two params (deviceId, workSessionId) are covered by their own schema descriptions.

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

Purpose5/5

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

States a specific verb (Find) and resource (files and folders by name), and immediately scopes the matching semantics (case-insensitive substring, glob when * or ? present). It is clearly distinguishable from siblings like search_content (contents) and list_directory (enumeration).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives concrete usage conditions: path defaults to the work session workspace or ~, and advises giving the most specific folder to avoid the 8-second timeout truncation. It does not explicitly name an alternative (e.g. search_content for contents) so routing is implied rather than stated.

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

All BCD — Bridge Control Delegate tools Inspect

Try in Browser

Let your AI agent see the webWeb-to-screenshot MCP for Claude, Cursor and Codex. No cookie banners. Free to start.snap-render.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?