Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
CELLAR_DOOR_SERVER_POLICYNoServer-side admission policy override. Values: OPEN_DOOR, STRICT, EMERGENCY_ONLY. If set, any LLM-provided admissionPolicy parameter is ignored.STRICT

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
generate_identityA

Generate a new Ed25519 DID keypair for signing EXIT markers

quick_exitA

One-shot create and sign a departure marker. Generates a new identity if none exists.

create_exit_markerB

Create and sign a departure marker. Uses session identity or generates a new one.

verify_exit_markerB

Verify a signed EXIT marker from its JSON representation

counter_sign_exit_markerB

Add a counter-signature to a signed EXIT marker, attesting agreement with the departure record

verify_and_admitA

Verify an EXIT marker, evaluate an admission policy, and create a signed arrival marker

evaluate_admissionA

Check whether an EXIT marker meets an admission policy without creating an arrival

verify_transferB

Verify a complete EXIT→ENTRY transfer: check both markers and continuity

list_admission_policiesA

List available admission policy presets and their configurations

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.7/5.0

Scored across 9 tools

Disambiguation5/5

Each tool has a clearly distinct purpose: creating, counter-signing, verifying, admitting, and generating identities. No two tools overlap in functionality.

Naming Consistency5/5

All tool names consistently use the verb_noun pattern with underscores (e.g., create_exit_marker, verify_and_admit), making the set predictable and easy to navigate.

Tool Count5/5

With 9 tools covering the core workflows of creating, verifying, admitting, and transferring EXIT markers, the count is well-scoped and each tool earns its place.

Completeness4/5

The tool set covers the main lifecycle: creation, verification, admission, and transfer. Minor gaps exist, such as no tool to manage admission policies beyond listing, but the core functionality is complete.

Maintenance

ActivityInactive
ResponsivenessNo issues