Skip to main content
Glama

Glob Files

glob_files

Find files by glob pattern while automatically filtering noise like node_modules and .git, so you can locate project files quickly.

Instructions

Find files matching a glob pattern (e.g. '/*.ts', 'src//*.py') with automatic noise filtering.

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": {
      "pattern": "<pattern>"
    },
    "name": "glob_files"
  }
}

Input Schema

NameRequiredDescriptionDefault
patternYesGlob pattern (e.g. '**/*.py', 'src/**/*.ts', '*.json').
base_pathNoDirectory to search from (default: current directory)..
include_hiddenNoIf True, includes .git, node_modules, .venv files.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.1.0
    • addedInput schema / properties / include_hidden
      Added value: +{
      +  "default": false,
      +  "description": "If True, includes .git, node_modules, .venv files.",
      +  "type": "boolean"
      +}
  2. First observedv2.0.0

TDQS

B3.4/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, yet it only vaguely claims "automatic noise filtering" — the actual filtering semantics (.git, node_modules, .venv) are documented in the include_hidden parameter, not the description. It says nothing about read-only safety, symlink or recursion behavior, or error conditions when the base path does not exist.

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, and the core verb+resource leads. The trailing clause "with automatic noise filtering" is slightly vague but relevant enough to keep, and the overall length suits a three-parameter lookup tool.

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?

For a low-complexity, three-parameter tool with a required pattern and a defaulted search root, the description plus a complete schema and an output schema cover what an agent needs to call it correctly. Only sibling routing guidance is missing, which is scored under usage guidelines rather than here.

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 description coverage is 100%, so pattern, base_path, and include_hidden are already fully documented with examples and defaults. The description repeats the pattern example verbatim from the schema and adds no meaning beyond it, which is the expected baseline given complete schema coverage.

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 states a specific verb and resource ("Find files matching a glob pattern") and illustrates the pattern syntax with two concrete examples. An agent can distinguish this from content-searching siblings like search_code, but the description never names or contrasts 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.

Usage Guidelines3/5

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

Usage is only implied by the stated purpose: it is obviously a filename-pattern tool, whereas search_code searches content and list_directory enumerates one directory. There is no explicit when-to-use/when-not-to-use guidance and no mention of when a sibling such as list_directory would be preferable.

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