Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
ECLIPSE_CLUSTER_TRUSTNoTrust bundle: the public keys the gate trusts at all. Start from trust-bundle.example.json../trust-bundle.json
ECLIPSE_CLUSTER_POLICIESNoDirectory of policy JSON files (see policies/default.json, policies/signature-only.json)../policies/
ECLIPSE_CLUSTER_RECEIPTSNoAppend-only receipt ledger (hash-chained)../receipts.jsonl

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
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
verify_imageA

Verify a container image against policy BEFORE it is allowed anywhere near a runtime: registry allowlist, digest resolution, cosign-style signature validity, signer named by policy, payload binding, and DSSE provenance. Returns a per-check PASS/FAIL verdict and appends a receipt. Fails closed on every error.

policy_showB

Show the loaded verification policies, the trust bundle's public keys (fingerprints only), and config paths. The written scope the gate enforces.

receipt_listC

The append-only, hash-chained receipt ledger of past verifications — passes and failures alike.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.4/5.0

Scored across 3 tools

Disambiguation5/5

Each tool targets a distinct object and action: verifying an image, inspecting loaded policies, and listing the receipt ledger. There is no plausible way to confuse them, and the descriptions reinforce the boundaries (action vs. configuration vs. audit trail).

Naming Consistency4/5

All three names are snake_case and readable, but the ordering convention is mixed: verify_image is verb_noun while policy_show and receipt_list are noun_verb. It is consistent enough to predict, but not a single uniform pattern.

Tool Count4/5

Three tools is on the lean side but fits the narrow scope of a verification gate: verify, inspect policy, read ledger. Each tool clearly earns its place with no filler.

Completeness4/5

The core lifecycle — gate on verify, inspect the policy being enforced, audit past verdicts — is fully covered with a fail-closed design. Minor gaps exist, such as fetching a single receipt by ID or a policy reload/validation operation, but agents can work around them via receipt_list and policy_show.

Maintenance

ActivityMaintained
ResponsivenessNo issues