Skip to main content
Glama

fs_glob

Read-onlyIdempotent

Match file paths against a glob pattern. Fast metadata query — no file contents are read, no scan.

Supported syntax: * (not across /), ** (across /), ? (one char), {a,b,c} (brace expansion).

Example:

// All TypeScript files under src/api:
{ "project_id": "my-saas", "pattern": "/src/api/**/*.ts" }

// JS or TS top-level files:
{ "project_id": "my-saas", "pattern": "/*.{js,ts}" }

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

Input Schema

NameRequiredDescriptionDefault
limitNoMax matches to return (default 500, cap 5000).
patternYesGlob pattern. Leading slash is added if missing.
project_idYesProject ID (UUID), subdomain, or slug — resolved server-side, no UUID lookup needed. 'default' also works when the account has exactly one project; multi-project accounts must name one (the error lists them).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint, so the safety profile is covered; the description adds genuinely new behavioral context by emphasizing this is a fast metadata query that reads no file contents and performs no scan. It does not describe the return shape or whether results are ordered, which is the remaining 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?

The core capability is front-loaded in the first sentence, followed by a compact syntax reference and two short examples. The examples carry information the prose doesn't, though the block could be trimmed slightly without loss.

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

Completeness4/5

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

With no output schema, the description should clarify what comes back; it implies matches are returned as file paths and the schema's limit parameter covers volume, but the exact result shape (paths vs. objects, ordering) is left unstated. For a simple read-only glob tool this is a minor omission rather than a blocking one.

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 100%, so baseline is 3, but the description goes further by documenting glob syntax (`*`, `**`, `?`, `{a,b,c}`) and showing concrete pattern/project_id combinations in the examples. That adds real meaning beyond the schema's terse "Glob pattern. Leading slash is added if missing."

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 and resource ("Match file paths against a glob pattern") and immediately scopes it as a metadata-only query with "no file contents are read, no scan," which implicitly separates it from content-searching siblings like fs_search and content-reading tools like fs_read.

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?

The "no file contents are read, no scan" clause signals the appropriate use case, and the two examples show realistic invocation contexts. However, it never explicitly names an alternative (e.g. fs_search) or states when-not to use it, leaving the agent to infer the boundary.

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