bb_globNeed to locate files by pattern? Recursively search a directory for files matching a glob like **/*.json or *.png. Requires file-system permission.
Recursively find files under a directory matching a glob such as "**/.json" or ".png". Needs file-system permission.
| Name | Required | Description | Default |
|---|---|---|---|
| path | Yes | ||
| limit | No | ||
| pattern | Yes |
Changes observed during successful MCP inspections.
v2.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It usefully discloses recursion and the file-system permission requirement, but says nothing about the default limit of 200, truncation/pagination behavior, symlink handling, or what happens when nothing matches.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two compact sentences; the core action is front-loaded and the permission caveat is a short trailing clause. No filler.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a 3-parameter tool with no output schema and no annotations, the description covers the essentials of what and how, but omits result-limiting behavior and error/empty-result semantics that an agent would need to call it reliably.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, so the description must compensate. It clarifies 'path' as a directory and 'pattern' as a glob with examples, but leaves the 'limit' parameter (default 200) entirely undocumented in both schema and description.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb+resource ('recursively find files') plus the matching semantics, with concrete glob examples ("**/*.json", "*.png"). It is distinguishable from bb_list_dir and bb_read_file, though it never names those siblings explicitly.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The glob examples imply the intended use case (pattern-based discovery vs. simple listing), and the permission prerequisite is stated. However, there is no explicit when-to-use guidance or comparison against bb_list_dir/bb_file_info for the same directory.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.