Skip to main content
Glama
minheyok-choi

file-analysis-mcp

analyze_folder_structure

Read-onlyIdempotent

Analyzes a folder's subdirectory tree, file counts by extension, total size, and largest file to reveal how the folder is organized. Use to grasp folder structure before deeper inspection.

Instructions

폴더의 하위 디렉터리 트리와 확장자별 통계, 용량, 최대 파일을 분석합니다.

scan_folder보다 한 단계 더 깊은 "구조" 파악용 도구입니다. 폴더가 어떻게 구성돼 있는지(하위 폴더별 파일 분포, 가장 큰 파일 등)를 먼저 감 잡고 싶을 때 사용하세요.

Returns: FolderStructureResponse: tree{"하위폴더명": {...}, "_files": [...]} 형태의 중첩 딕셔너리입니다. 파일이 max_files보다 많으면 tree에는 앞쪽 max_files개만 반영되고 list_truncated=True가 되지만, total_files/ by_extension/total_size_bytes 등 통계는 항상 전체 파일 기준입니다.

Examples: - 사용: "이 폴더 구조 좀 분석해줘", "가장 큰 파일이 뭐야?" - 사용하지 않음: 파일 목록만 빠르게 보고 싶을 때 → scan_folder

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
max_filesNo트리(tree)에 포함할 최대 파일 수(컨텍스트 보호용 상한). 통계(개수/용량 등)는 상한과 무관하게 항상 전체 기준입니다.
extensionsNo필터링할 확장자 목록. 생략하면 pdf/docx/pptx/svg/png 전체를 대상으로 함
folder_pathYes분석할 폴더의 절대 경로

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
treeYes
folderYes
statusYesOK 또는 PARTIAL 등 처리 결과 상태
max_depthYes
total_filesYes조건에 맞는 전체 파일 수(통계는 항상 전체 기준)
by_extensionYes
next_actionsNo
largest_filesYes
list_truncatedYes파일이 너무 많아 tree에는 max_files개까지만 반영됐으면 True
total_size_bytesYes
Behavior5/5

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

Annotations already declare readOnly, idempotent, and non-destructive. The description adds crucial behavioral detail beyond that: it explains that the tree includes only up to max_files entries with list_truncated flag, while statistics are always based on the full file set. It also details the default extension set when no filter is given. No contradiction with annotations; this transparency is valuable.

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-organized: opens with the core purpose, then a usage hint, a Returns section, and examples. Each section contributes to understanding, though it is slightly longer than strictly necessary. The structure is front-loaded with the main purpose and comparison, making it easy to skim. Optimally concise for the complexity it covers.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present and safety annotations provided, the description still adds essential behavioral details (truncation semantics, stats being global) and usage examples. It covers the necessary context for correct invocation, including how max_files affects results and the default extension pool. No missing critical information for typical usage.

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 100%, with each parameter already having detailed descriptions (folder_path as absolute path, max_files with truncation explanation, extensions with default set). The tool description does not add supplementary meaning beyond the schema; it neither repeats nor enhances parameter semantics, so the baseline 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 clearly states it analyzes the folder's subdirectory tree, extension statistics, size, and largest files, with a specific verb and resource. It distinguishes itself from scan_folder by noting it goes one level deeper into structure. However, it does not differentiate from the similarly named sibling analyze_folder, which could create ambiguity about which tool to use.

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 explicit guidance: use it when you need an understanding of folder organization (subfolder distribution, largest files) and explicitly says not to use it when you only need a quick file list, directing to scan_folder. However, it omits any comparison with analyze_folder, another sibling that might be a relevant alternative, leaving some usage ambiguity.

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/minheyok-choi/fileanalyzer_mcp-testmonial'

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