Skip to main content
Glama
kridaydave

File Organizer MCP

by kridaydave

Batch Read Files for LLM Context

file_organizer_batch_read_files
Read-onlyIdempotent

Reads all files in a folder to provide LLM context, extracting text content and media metadata, with filtering and size limits for efficient batch processing.

Instructions

Reads contents of all files in a specified folder for LLM context. For text files (documents, code, notes), reads the actual content. For media files (audio, video, images), reads metadata instead of binary content. Provides a comprehensive summary of folder contents.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
directoryYesFull path to the directory
max_filesNoMaximum files to process (safety limit)
file_typesNoFilter by file extensions (e.g., [".txt", ".pdf"])
include_contentNoInclude text content
include_subdirsNoInclude subdirectories
response_formatNomarkdown
include_metadataNoInclude metadata
max_file_size_mbNoMax file size in MB to read content
Install Server

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, covering safety. The description adds valuable behavioral details: it reads content for text files, metadata for media files, and provides a comprehensive summary. This goes beyond the annotations by explaining the actual processing logic and output nature, which is not implied by the structured fields.

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?

The description is three focused sentences with no redundancy. The main purpose is front-loaded, followed by the key behavioral nuance (text vs media) and the output characteristic. Every sentence adds meaningful information, making it concise and well-structured.

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?

For a tool with 8 parameters, the schema covers 88% of them, and the description explains the core behavior and output. It states that it reads content or metadata and provides a summary, which is sufficient for an agent to understand the tool's function. It does not mention return format or specific error cases, but these are either covered by schema defaults or not critical for selection/invocation. Overall, it is fairly complete.

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 description coverage is 88%, so the parameters are well-documented in the schema. The description does not elaborate on parameters like max_files, file_types, or include_content, but it doesn't need to since the schema covers them. The description's main added value is the text vs media distinction, which is behavioral rather than parameter-specific. Baseline 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 a specific verb ('Reads'), resource ('contents of all files in a specified folder'), and a purpose ('for LLM context'). It distinguishes itself from siblings like file_organizer_read_file by emphasizing batch reading of a folder versus a single file, and also differentiates its handling of text vs media files. This gives the agent a precise understanding of the tool's role.

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 for when to use the tool: when you need folder contents for LLM context, including a note on how it handles different file types. It does not explicitly list exclusions or name alternatives, but the context is specific enough to guide selection away from single-file reads and towards batch operations.

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

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/kridaydave/File-Organizer-MCP'

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