Skip to main content
Glama

ui_browse_dir

Browse local directories and files to power a UI path picker, filtering by query, extensions, hidden items, and optional file inclusion.

Instructions

App-only: browse local directories and files for the UI path picker.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "ui_browse_dir"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathNo
queryNo
extensionsNo
include_filesNo
include_hiddenNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. 'Browse' implies a read operation, but nothing confirms read-only semantics, recursion depth, how errors on invalid paths are handled, whether hidden/ignored entries are filtered by default, or what the response looks like. For a 5-parameter filesystem tool with zero annotation coverage, this is a substantial gap.

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?

A single front-loaded sentence with no filler; 'App-only' comes first, which is the most important constraint. It is efficient, though the terseness is arguably under-specification rather than disciplined concision.

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?

Five optional parameters, no annotations, no output schema, and no schema descriptions leave the description as the only source of information, and it covers none of the parameter or return behavior. An agent can guess the intent but cannot confidently determine filtering semantics or output shape.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and all five parameters (path, query, extensions, include_files, include_hidden) are undocumented in both schema and description. The parameter names are largely self-explanatory, which prevents a 1, but the description adds no meaning such as whether 'query' is a substring or glob match, how 'extensions' interacts with 'include_files', or what the default path is when none is given.

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 supplies a specific verb (browse) and resource (local directories and files), plus a scope qualifier ('App-only') and a stated purpose ('for the UI path picker'). It is clearly distinct from the state-mutation siblings like ui_create_project or ui_save_note, though it does not name any sibling explicitly.

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?

'App-only' and 'for the UI path picker' imply the context in which this tool is appropriate, which is more than nothing. However, there is no explicit when-to-use/when-not-to-use guidance, no mention of what the agent should do instead if it is not in the app context, and no prerequisites stated.

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