Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

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

CapabilityDetails
tools
{
  "listChanged": false
}

Tools

Functions exposed to the LLM to take actions

NameDescription
evaluate_fdiaB

Evaluates action requests through deterministic ZK-FDIA equation F = (D^I) * A and enterprise custom policy rules.

configure_policyC

Configures or updates Enterprise Custom Policy rules for parameter A.

rct_thinkA

Executes authentic Delentia 7-Stage Reverse Component Thinking mental OS to eliminate hallucination.

compress_contextA

Compresses verbose conversation history by extracting state deltas (74.2% - 91.5% token reduction).

orchestrate_swarmB

Encapsulates objectives into JITNA packets and coordinates 1+4 Specialized Pillar Agents (Router, Guardian, Executor, Scribe).

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.5/5.0

Scored across 5 tools

Disambiguation5/5

Each tool addresses a distinct operation—policy evaluation, policy configuration, metacognitive reasoning, context compression, and swarm orchestration. evaluate_fdia and configure_policy are related but not interchangeable.

Naming Consistency4/5

Four tools follow a clear verb_noun pattern: evaluate_fdia, configure_policy, compress_context, orchestrate_swarm. rct_think inverts the object before the verb, a minor inconsistency.

Tool Count5/5

Five tools is an appropriately small set for a sovereign-agent utility server. Each tool covers a distinct area without redundancy.

Completeness3/5

Core operations exist for policy evaluation, policy configuration, thinking, context compression, and orchestration. However, lifecycle support is thin: there is no policy retrieval/deletion, no swarm status or result collection, and compressed context lacks a restoration counterpart.

Maintenance

ActivityMaintained
ResponsivenessNo issues