Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
DELIVERY_DRY_RUNNoIf set to 'true', runs task delivery in dry-run mode without side effects.

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
prepare_deliveryA

Prepare a side-effect-free delivery preview from local git and supplied Jira context.

compose_jira_updateD

Render a Jira update after a real GitLab merge request exists.

finalize_deliveryC

Persist final GitLab and Jira results, release notes, and sanitized evidence.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3/5.0

Scored across 3 tools

Disambiguation5/5

Each tool targets a distinct phase of the delivery workflow: prepare creates a preview without side effects, compose generates a Jira update after a merge, and finalize persists results. There is no overlap in their purposes or expected inputs.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern (prepare, compose, finalize) with clear action-first naming. The style is uniform and predictable.

Tool Count4/5

With three tools, the server is slightly lean but well-scoped to the core delivery lifecycle. Each tool is necessary and the count feels reasonable for the narrow, focused purpose.

Completeness4/5

The workflow covers prepare, compose, and finalize, which form a complete pipeline from preview to persistence. Minor gaps like status checks or cancellation are absent but not critical to the primary delivery flow.

Maintenance

ActivityInactive
ResponsivenessNo issues