Skip to main content
Glama

Find files by pattern

glob_files
Read-onlyIdempotent

List all project file paths (optional substring filter)

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": "glob_files"
  }
}

Input Schema

NameRequiredDescriptionDefault
filterNoSubstring or glob-ish filter
project_idNoProject id (or use session from use_project)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world, so safety is covered. The description contributes that the default result is the full path listing and filtering is optional, but says nothing about result size, truncation, or whether the walk is recursive — meaningful for a project-wide listing.

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 phrase with the optional parameter noted in parentheses; nothing is wasted. It is arguably too sparse rather than padded, which is a completeness issue rather than a conciseness one.

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

Completeness3/5

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

With only two fully described parameters and rich annotations, little more is strictly required, and the description does say the output is file paths. Still missing are the pattern-matching semantics and any note on scope or size limits, which an agent needs to call this correctly on a large project.

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 100%, so both parameters are documented and the baseline is 3. The description narrows the ambiguity of the schema's "Substring or glob-ish filter" toward a plain substring match and confirms the filter is optional, but leaves the glob behavior and the project_id-vs-session fallback entirely to the schema.

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

Purpose3/5

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

The description gives a concrete verb and resource ("List all project file paths") plus the optional filter, so the basic operation is graspable. But it does not reconcile the glob semantics implied by the name/title "Find files by pattern" with the "substring filter" it describes, and it never distinguishes this tool from close siblings like list_files or search_files.

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

Usage Guidelines2/5

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

Only the phrase "optional substring filter" hints at how to use it (call with no filter to get everything). There is no explicit guidance on when to choose this over list_files or search_files, and no stated preconditions such as whether a project_id or active session is needed.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources