fleet-immune-system
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 |
|---|---|
| immune_discoverC | Discover co-occurring emergent fleet threat patterns from normalized defensive scan signals. |
| immune_synthesizeB | Synthesize a non-executing defensive antibody recipe from a threat pattern. |
| immune_cycleC | Plan one fleet immune cycle with variants, memory recall and adjacent cohort targeting. |
| immune_crystallizeB | Persist a successful pattern/antibody outcome into the server-local immune memory for later recall. |
| immune_recallC | Recall the closest retained immune-memory crystal for a threat pattern. |
| immune_breedB | Breed two non-executing antibody recipes into a deterministic next-generation candidate without escalating destructive action. |
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 6 tools
Each tool targets a distinct stage in the immune-system workflow: discovery, synthesis, planning, persistence, recall, and breeding. While synthesize and breed both produce antibody recipes, their inputs and methods differ clearly in the descriptions.
All tool names follow the same immune_<verb> pattern using lowercase snake_case. The verbs are varied but consistently placed, making the naming scheme predictable and readable.
Six tools is well-scoped for an immune-system domain, covering the main phases without redundancy or bloat. Each tool earns its place in the workflow.
The core lifecycle is covered: discover, synthesize, plan, persist, recall, and breed. A minor gap is lack of memory deletion or invalidation, but this is not essential to the described non-executing defensive purpose.