Skip to main content
Glama
pozii
by pozii

summarize_file

Summarize files or directories using minimal tokens, extracting structure and content to reduce AI processing costs.

Instructions

Summarize a file or directory without reading every byte. Agents get full structural understanding in ~500 tokens instead of 50,000+.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYesAbsolute path to a file or directory.
max_tokensNoTotal output budget in tokens.
modeNo"content" (summary of text), "structure" (tree only), "both".both
file_extensionsNoFilter by extensions like [".py", ".md"] (directory only).
max_depthNoDirectory traversal depth limit.
modelNoUsed for token counting.gpt-4o

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior2/5

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

No annotations provided. Description only mentions token efficiency but does not disclose behavioral traits such as permissions, limits, or what happens with non-text files.

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?

Two sentences, 17 words, front-loaded with purpose. Every sentence adds value with zero redundancy.

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?

Moderate complexity with 6 params and output schema present. Description is minimal but schema covers parameters. Lacks usage guidance and behavioral context needed for full completeness.

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%, so baseline is 3. Description does not add new meaning to parameters beyond what schema already provides.

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?

Clearly states verb 'summarize' and resource 'file or directory', distinguishes from reading every byte, and highlights efficiency benefit of ~500 tokens vs 50,000+.

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

Usage Guidelines2/5

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

No explicit guidance on when to use this tool versus siblings like compress_context or extract_webpage. No when-not-to-use or alternative naming.

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/pozii/tokensaver'

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