Skip to main content
Glama

local_summarize

Summarize large files or text locally to save Claude quota. Reads file content server-side; returns a concise summary without sending full content to Claude.

Instructions

PREFIERE esta tool en vez de leer el archivo con Read cuando el archivo es grande (>200 líneas / >10 KB) y solo necesitas un resumen, no el contenido literal.

Resume texto o el contenido de un archivo con un modelo local, sin gastar contexto de Claude.

Usa esto para resumir archivos/documentos grandes: pasa 'path' y el archivo se lee del lado
del servidor, de modo que el contenido completo NO entra al contexto de Claude (solo vuelve el
resumen corto). Alternativamente pasa 'text'. Enruta al modelo mecánico (entradas cortas) o al
modelo de contexto largo (documentos grandes) automáticamente.

Args:
    text: Texto a resumir (usa esto o 'path').
    path: Ruta a un archivo cuyo contenido se resume (leído server-side).
    max_words: Longitud máxima del resumen en palabras.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathNo
textNo
max_wordsNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

No annotations are provided, so the description carries the full burden. It discloses that files are read server-side, preventing the full content from entering Claude's context, and mentions automatic model routing based on input size. This is comprehensive but could add more about latency or limitations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is somewhat verbose, especially the opening phrase in Spanish. It could be more concise while retaining key information. The structure is clear but not optimally front-loaded.

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?

Given the complexity of the tool (3 parameters, no required ones, output schema present), the description covers the essential aspects: input options, model routing, and context-saving behavior. It is complete enough for an agent to use correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% (no parameter descriptions in schema), but the description compensates by explaining each parameter's purpose: 'text' for direct input, 'path' for server-side file reading, and 'max_words' for summary length. It also explains the trade-off between the two input methods.

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 that the tool summarizes large files or text using a local model to save Claude's context. It explicitly distinguishes itself from the Read tool by specifying when to prefer it.

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 provides explicit usage guidance: prefer this over Read for files >200 lines or >10 KB, and explains the context-saving benefit. It also clarifies the two input options (text or path) and automatic routing to appropriate models.

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/ZahiriNatZuke/local-delegate'

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