Skip to main content
Glama
marksolly

Code Index MCP

by marksolly

find_files

Locate files matching glob patterns to quickly verify existence or find specific files in a codebase.

Instructions

Find files matching a glob pattern using efficient directory tree traversal.

Use when:
- Looking for files by pattern (e.g., "*.py", "test_*.js", "src/**/*.ts")
- Searching by filename only (e.g., "README.md" finds all README files)
- Checking if specific files exist in the project
- Getting file lists for further analysis

Pattern matching:
- Supports both full path and filename-only matching
- Uses forward slashes consistently across all platforms
- Efficient directory tree traversal for better performance

Args:
    pattern: Glob pattern to match files (e.g., "*.py", "test_*.js", "README.md")

Returns:
    Dictionary with files list and status information

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
patternYes
Behavior2/5

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

No annotations are provided, so the description bears full responsibility for behavioral disclosure. It mentions 'efficient directory tree traversal' and cross-platform slash handling but omits details like search scope (e.g., whether hidden files are included) and whether the traversal is recursive by default.

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 description is well-structured with sections for primary function, use cases, pattern notes, args, and returns. It is concise yet informative, though the 'Use when' list could be slightly more compact.

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?

Given the simplicity of the tool (one parameter, no output schema), the description covers purpose and usage adequately. However, it does not specify the search scope (e.g., project root) or behavior regarding hidden files, leaving some gaps for the agent.

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 0%, but the description compensates with examples (e.g., '*.py', 'README.md') and explains that the pattern supports full path and filename-only matching. This adds meaning beyond the raw schema definition, though more detail on glob syntax would improve it.

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?

The description clearly states the tool's purpose: finding files matching a glob pattern using efficient directory tree traversal. The verb 'Find' and resource 'files matching a glob pattern' are specific and distinguish it from sibling tools like search_code_advanced which searches code content.

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 'Use when' section provides clear scenarios for using the tool, such as looking by pattern or checking existence. However, it lacks guidance on when not to use it or explicit differentiation from sibling tools, leaving the agent to infer context.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/marksolly/code-scope-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server