Skip to main content
Glama

glob

Read-onlyIdempotent

Find files on a remote machine by pattern, including recursive ** matches, with results sorted newest first and .gitignore rules honored.

Instructions

Find files on the remote machine by glob pattern (** supported); newest first, .gitignore honoured.

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

Input Schema

NameRequiredDescriptionDefault
pathNoDirectory to search. Default: the workspace directory.
fleetNoFleet name. Omit to use the default.
contextNoContext name. Omit to use the default.
patternYesGlob pattern, e.g. **/*.go. Results are sorted by modification time, newest first.
workspaceNoWorkspace id. Omit to use this session's workspace on the fleet.

Output Schema

NameRequiredDescriptionDefault
kindYes
mimeNo
noteNo
pathNo
sizeNo
countNo
linesNo
whereYes
sha256No
contentNo
entriesNo
new_fileNo
warningsNo
truncatedNo
workspaceYes
next_offsetNo
total_linesNo
omitted_bytesNo
written_bytesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Beyond the readOnly/idempotent/non-destructive annotations, the description discloses two genuinely useful behaviors: results are ordered newest first, and .gitignore is honoured (so matches are silently filtered). It does not mention result caps, truncation, or how a remote fleet failure surfaces, keeping it below 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single dense sentence, front-loaded with the action and mechanism, then the two behavioral facts an agent most needs. Nothing is redundant with the schema or padded.

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?

An output schema exists, so return values need no explanation, and all parameters are documented in the schema. The remaining gap is scale behavior (limits, truncation, empty-match semantics), which matters for a glob over a remote tree but is not addressed.

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 all five parameters are already documented, including the newest-first sorting note on `pattern`. "Remote machine" adds a little framing for the fleet/context/workspace parameters but the description does not explain their relationship, so it sits at the schema-driven baseline.

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?

States a specific verb and resource ("Find files"), the mechanism (glob pattern, with ** explicitly supported), and the target ("remote machine"). It implicitly separates itself from ls/grep by being pattern-based search, but never names a sibling, so it stops short of the top score.

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: an agent can infer this is for locating files by pattern rather than listing a directory or searching contents, but there is no explicit when-to-use/when-not guidance or pointer to ls/grep for the adjacent cases.

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