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
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
daedalus_initB

Escanea el workspace actual, crea templates reutilizables si faltan y genera agents.config.yaml + agents/ por proyecto sin pisar archivos existentes.

daedalus_listProjectsB

Lista los proyectos detectados por /daedalus init en el workspace actual.

daedalus_listGroupsB

Lista grupos disponibles como all, java-all o angular-all generados por /daedalus init.

daedalus_runA

Ejecuta un pipeline como plan sobre un grupo o lista de proyectos y devuelve un reporte por agente/proyecto.

daedalusB

Parser conveniente para comandos estilo /daedalus init, /daedalus listProjects, /daedalus plan --group:java-all "tarea" o /daedalus plan --project [a,b] "tarea". También acepta /agent por compatibilidad.

agent_initD

Alias legacy de daedalus_init.

agentD

Alias legacy de daedalus. Acepta /agent y /daedalus.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

C2.3/5.0

Scored across 7 tools

Disambiguation2/5

Multiple tools serve as aliases (agent vs daedalus, agent_init vs daedalus_init), causing ambiguity. An agent can't easily distinguish which parser to use for command interpretation.

Naming Consistency2/5

Names mix daedalus_ prefix (daedalus_init, daedalus_listGroups) with bare names (agent, agent_init) and inconsistent styles (agent vs daedalus). No uniform pattern.

Tool Count4/5

7 tools is appropriate for a project management assistant, covering initialization, listing, and execution. Not excessive or insufficient.

Completeness3/5

Core operations (init, list, run) are present, but missing update/delete actions for projects or groups. Coverage is adequate but not full CRUD.

Maintenance

ActivityInactive
ResponsivenessNo issues