chrysalide-mcp
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 | {
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| chrysalide_start_taskB | Démarre un nouveau job Chrysalide. Retourne immédiatement avec un job_id. |
| chrysalide_get_statusB | Retourne l'état courant d'un job. Non-bloquant. |
| chrysalide_get_reportA | Retourne le rapport final. À appeler seulement quand le job est terminé. |
| chrysalide_cancel_taskB | Annule un job en cours. La sandbox est conservée pour inspection. |
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 4 tools
Each tool targets a distinct action: start a job, check status, cancel a job, and fetch the report. The lifecycle states are clearly enumerated in descriptions (running, finished, cancelled), leaving no ambiguity about which tool to call at any point.
All tools follow a consistent verb_noun pattern with a uniform prefix (chrysalide_get_status, chrysalide_get_report, chrysalide_cancel_task, chrysalide_start_task). Verbs are all action-oriented and snake_case is used consistently throughout.
Four tools is a reasonable, focused set for a job-management server covering start, status, report, and cancellation. It's on the smaller end but each tool earns its place and the scope is appropriately narrow.
The job lifecycle is well covered: start, poll status, retrieve report, and cancel. A possible gap is the lack of a way to list historical jobs or re-fetch past reports, but the core lifecycle has no dead ends.