Skip to main content
Glama
Claude Free Code MCP

Claude Free Code MCP

by ImIpscanning

glob_files

Read-only

Finds files matching a glob pattern like src/**/*.js or */test.py, letting you locate code and assets across a workspace or subdirectory before reading or editing them.

Instructions

Find files matching a glob such as src/**/*.js, *.json or */test.py.

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

Input Schema

NameRequiredDescriptionDefault
globYesRelative glob pattern
limitNo1..500
directoryNoSearch subdirectory.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. Beyond that, the description adds nothing behavioral: it does not say whether the default limit of 100 truncates results, whether results are sorted, whether hidden/gitignored files are included, or what happens if the directory does not exist. For a search tool whose most common failure mode is silent truncation, this is a real gap.

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 sentence that front-loads the verb and resource and spends its remaining words on examples an agent can pattern-match against. There is no filler, hedging, or redundant restatement of the name.

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?

The tool is simple (3 params, 1 required, fully described schema, clear read-only annotations), so the description's brevity is largely appropriate. With no output schema, though, the description should at least sketch the return value (e.g. list of matching relative paths) and note the truncation behavior tied to `limit`. Those are the missing pieces an agent would need to use the results confidently.

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 three parameters are already documented in the schema. The description does add syntax-level meaning to `glob` (concrete patterns, including `**` recursion) that 'Relative glob pattern' alone does not fully convey. This is a marginal gain rather than a compensating one, so the baseline of 3 applies.

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 pairs a specific verb ('Find') with a specific resource ('files') and constrains the mechanism to glob patterns, backed by three concrete examples (src/**/*.js, *.json, **/test*.py). An agent can immediately tell this is a path-pattern search rather than reading, listing a tree, or mutating files. It stops short of naming a sibling (e.g. project_tree or read_files) to contrast against.

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 glob examples implicitly convey that this is pattern-based discovery, including recursive `**` usage, which helps an agent pick it over a plain directory listing. However, there is no explicit when-to-use statement, no when-not-to-use exclusion, and no mention of alternatives such as project_tree for full traversal or read_files for contents.

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