Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
procesarB

Delega UNA tarea de procesamiento acotada al cluster local (0 tokens cloud). Pasa rutas en archivos en vez de pegar su contenido: se leen localmente. Para: boilerplate, docstrings, conversiones de formato, mensajes de commit, borradores.

loteC

Delega VARIAS tareas independientes a la vez: se reparten entre los nodos del cluster y corren en paralelo.

revisar_archivosB

Primera pasada de code review sobre rutas de archivos (un nodo por archivo, en paralelo). Devuelve solo los hallazgos: los archivos no pasan por tu contexto.

resumir_archivosA

Resume o extrae información de archivos por ruta (en paralelo) sin que pasen por tu contexto.

estadoA

Salud del cluster y total de tokens cloud ahorrados.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.3/5.0

Scored across 5 tools

Disambiguation5/5

Each tool targets a distinct operation: cluster health, batch parallel tasks, single processing, summarization, and code review. No overlaps; descriptions clarify differences.

Naming Consistency3/5

Tool names mix nouns (estado, lote) and verbs (procesar, resumir_archivos, revisar_archivos). While the verb_noun pattern is consistent for two tools, the overall pattern is inconsistent.

Tool Count5/5

Five tools is well-scoped for the server's purpose of local cluster processing and file analysis. Each tool serves a necessary function without bloat.

Completeness4/5

Covers core workflows: cluster health, batch and single task processing, summarization, and code review. Missing job management (e.g., cancel/status) is a minor gap but not critical.

Maintenance

ActivityStale
ResponsivenessNo issues