Skip to main content
Glama
Sign In
MCP Filesystem Python

MCP Filesystem Python

by gary109
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

search-files

Search for files containing specific text. Filter by file pattern to narrow results.

Instructions

Search for files containing specific text

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": {
      "query": "<query>"
    },
    "name": "search-files"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesText to search for
file_patternNoFile pattern to filter search (e.g., *.py for Python files)*

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior2/5

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

No annotations are provided, so the description carries full burden. It only states the basic function but omits important details like search scope (recursive?), case sensitivity, performance implications, or that it searches file contents (not names). The agent has limited behavioral context.

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 a single, concise sentence that gets the point across. However, it could be slightly more detailed without losing conciseness (e.g., 'within a directory').

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 with two parameters and no output schema. The description gives the core purpose but misses details like default path (current directory), behavior with no match, and whether it searches file names or contents. It's adequate but has gaps.

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% with clear parameter descriptions for 'query' and 'file_pattern'. The description adds no additional meaning beyond the schema, so baseline of 3 is appropriate.

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 searches for files by content ('containing specific text'). The verb 'Search' and resource 'files' are specific, and it distinguishes from siblings (delete-file, write-file) which have different purposes.

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

Usage Guidelines4/5

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

The description provides clear context that the tool finds files by text content. While it doesn't explicitly state when not to use it, the narrow focus and distinct sibling names make the appropriate usage clear.

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

Deploy Server

Other Tools