phases-agents
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
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
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| phases_agents_detectC | Detecte localement le profil borne d'une cible. N'execute aucun fichier. |
| phases_agents_get_skillC | Retourne le contenu borne d'un skill valide par identifiant. Aucun chemin libre n'est accepte. |
| phases_agents_list_skillsC | Decouvre et liste uniquement les packages de skills valides. |
| phases_agents_planB | Detecte une cible, charge le registre valide et rend un plan deterministe. N'execute aucun skill. |
| phases_agents_refresh_skillsC | Reconstruit explicitement un registre depuis les racines autorisees. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool targets a distinct operation: detect (profile), get_skill (read one), list_skills (enumerate), refresh_skills (rebuild registry), plan (produce a plan). The one soft overlap is that plan already performs detection, so an agent might wonder when to call detect versus plan directly.
All tools share the consistent phases_agents_ prefix followed by clear snake_case verbs/verb_noun forms (detect, get_skill, list_skills, plan, refresh_skills). No mixing of conventions.
Five tools is well-scoped for a skill-registry/planning domain, covering discovery, retrieval, detection, planning, and registry refresh without redundancy.
The surface covers the full read-side lifecycle: enumerate skills, read a skill, refresh the registry, detect a target, and produce a plan. It is read-only by design (no skill authoring/editing), which is a minor gap but consistent with the stated bounded-execution purpose.