Skip to main content
Glama
minheyok-choi

file-analysis-mcp

analyze_folder

Read-onlyIdempotent

Extract text from all PDF, DOCX, PPTX, SVG, and PNG files in a folder at once, returning a report with per-file status and errors. Handles partial failures and file limits transparently.

Instructions

폴더 안의 모든 대상 파일(pdf/docx/pptx/svg/png)을 한 번에 추출해 리포트로 반환합니다.

파일마다 read_document/read_image_text를 따로 호출하지 않아도 되는 배치 도구입니다. 한 파일이 실패해도 나머지 파일 처리는 계속되며, 실패 이유는 파일별로 남습니다. 파일 수가 max_files를 넘으면 앞쪽부터 max_files개만 처리하고, 넘겨받지 못한 개수는 skipped_due_to_limit로 투명하게 알려줍니다(조용히 누락되지 않습니다).

Returns: AnalyzeFolderResponse: reports[]의 각 항목은 status(OK/ERROR)와 함께 text 또는 error를 담습니다. status가 PARTIAL이면 일부 실패했거나(failed>0) 상한 때문에 스킵된 파일(skipped_due_to_limit>0)이 있다는 뜻입니다.

Examples: - 사용: "이 폴더 문서들 다 요약해줘", "폴더 구조 분석하고 내용도 정리해줘" - 사용하지 않음: 파일 목록만 필요할 때 → scan_folder - 사용하지 않음: 특정 파일 하나만 자세히 → read_document / read_image_text

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
max_filesNo이번 호출에서 실제로 추출을 시도할 최대 파일 수(컨텍스트/시간 보호용 상한). 초과분은 시도조차 하지 않고 skipped_due_to_limit로 개수를 알려줍니다.
recursiveNo하위 폴더까지 재귀적으로 탐색할지 여부
extensionsNo필터링할 확장자 목록. 생략하면 pdf/docx/pptx/svg/png 전체를 대상으로 함
folder_pathYes분석할 폴더의 절대 경로
max_chars_per_fileNo파일당 반환할 최대 문자 수(컨텍스트 보호용 절단)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
failedYes
folderYes
statusYesOK 또는 PARTIAL 등 처리 결과 상태
reportsYes
succeededYes
total_filesYes실제로 추출을 시도한 파일 수 (= len(reports))
next_actionsNo
total_matchedYes조건에 맞는 전체 파일 수(상한 적용 전)
skipped_due_to_limitYesmax_files 상한 때문에 시도조차 하지 않은 파일 수
Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint as safe. The description goes beyond by revealing that it is a batch tool that continues processing on per-file errors, transparently reports skipped files via skipped_due_to_limit, and returns statuses (OK/ERROR/PARTIAL). This adds significant behavioral context not present in annotations.

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: main purpose first, followed by batch/error/limit behavior, then return format, then examples. It is somewhat lengthy but every section adds value, including explicit '사용' and '사용하지 않음' examples. The front-loading of the core purpose is effective.

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?

Given the tool's complexity (5 parameters, output schema present), the description covers all essential aspects: batch semantics, failure handling, limit transparency, return structure, and usage alternatives. It also includes practical example prompts. Nothing an agent needs to correctly invoke the tool is missing.

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?

The input schema provides complete descriptions for all 5 parameters (100% coverage), so the baseline is 3. The description does not add new meaning to parameters beyond repeating max_files' skipped_due_to_limit behavior, which is already in the schema. No additional semantic value is provided.

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 extracts all target files (pdf/docx/pptx/svg/png) in a folder and returns a report. It explicitly distinguishes itself from siblings: scan_folder (file list only) and read_document/read_image_text (single file). The verb '추출' and resource '폴더' make the purpose specific and unambiguous.

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

Usage Guidelines5/5

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

The description explicitly states when to use the tool (batch extraction, folder document summarization) and when not to use it, naming the alternatives: scan_folder for file lists and read_document/read_image_text for individual files. It also clarifies behavior under max_files limit and partial failures, leaving no ambiguity about invocation 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/minheyok-choi/fileanalyzer_mcp-testmonial'

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