Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
OSIRIS_HOMENoSQLite database, reports, caches~/.osiris
OSIRIS_ROOTSNoRoots allowed for file reading (`;` separated)
OSIRIS_PYTHONNoPath to the Python runtime used by the npm launcher, which resolves the Python runtime in the order OSIRIS_PYTHON → uvx → python3 → python
OSIRIS_CACHE_TTL_SNoCache TTL (seconds)300
OSIRIS_DISPATCH_ONLYNoSet to 1 to expose only `osiris.call`0
OSIRIS_PRUNE_THRESHOLD_TOKENSNoPrune threshold40000

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
}
logging
{}
prompts
{
  "listChanged": true
}
resources
{
  "subscribe": false,
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
osiris.planC

Tache : plan, manifeste scelle. start | update | resume | status.

osiris.precheckB

Verifie une action avant qu'elle parte : invariant, doublon, budget.

osiris.observeC

Consigne une action : doublons, boucles, externalisation.

osiris.recallC

Rehydrate un ref, ou restitue l'etat / la memoire d'une tache.

osiris.checkpointC

Snapshot d'etat, ou cloture avec rapport, ou compaction.

osiris.handoffC

Contrat de delegation (create), ou son resultat (complete/collect).

Prompts

Interactive templates invoked by user choice

NameDescription
osiris/task-resumeModele de reprise de tache apres un crash ou un changement de contexte.

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3/5.0

Scored across 6 tools

Disambiguation4/5

The tools mostly map to distinct lifecycle phases: precheck before an action, observe after it, recall memory, checkpoint state snapshots/closure, handoff delegation, and plan task planning. Some boundary blur exists because checkpoint and recall both involve task state, and several tools bundle multiple sub-actions, but overall the purposes are separable.

Naming Consistency5/5

All tools follow the same osiris.<single_lowercase_concept> pattern with no mixing of casing or verb styles. The convention is predictable and readable across the entire set.

Tool Count5/5

Six tools is well-scoped for an agent governance/lifecycle server. Each tool corresponds to a meaningful phase or contract, and the count avoids both thinness and excessive surface area.

Completeness4/5

The set covers the core lifecycle: pre-action checks, observation, recall, checkpointing/closure, delegation handoff, and task planning. Minor gaps exist around explicit listing/inspection or cancellation operations, but agents can likely work around them through recall/status modes.

Maintenance

ActivityMaintained
ResponsivenessNo issues