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

Tools

Functions exposed to the LLM to take actions

NameDescription
cluster_of_file

Get architectural cluster data for a file path.

boundary_edges

Get fuse boundary edges touching a file or cluster.

high_coupling_seams

Get strongest cross-cluster seams for a file/cluster or whole repo.

impact_neighbors

Get likely architectural blast radius from symbol/file.

search_symbolsC

Search symbols via index DB if available, else graph fallback.

architecture_summaryC

Get compact architecture summary for context injection.

classify_promptC

Classify a prompt into scope and retrieval requirements.

guided_arch_contextC

Get staged architecture context with scope-first escalation gates.

task_fingerprintB

Translate natural-language task text into COV tokens.

behavioral_twinsC

Return top behavioral twin candidates ranked by COV overlap.

twin_contextC

Return task COV + top twins + seam + rubric for implementation guidance.

reload_artifactsA

Reload graph and fuse artifacts from disk.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.1/5.0

Scored across 8 tools

Disambiguation4/5

Most tools have distinct purposes, but architecture_summary and guided_arch_context both provide architectural context, and behavioral_twins and twin_context both involve twins, which could cause confusion. Descriptions help differentiate by emphasizing different outputs and use cases.

Naming Consistency4/5

All tool names use consistent snake_case and lowercase style. However, the naming pattern mixes verbs (classify, reload, search) and nouns (architecture_summary, behavioral_twins, twin_context), which is slightly inconsistent.

Tool Count5/5

With 8 tools, the server covers a reasonable scope for architecture indexing and context retrieval without being bloated or too sparse. Each tool serves a clear purpose within the workflow.

Completeness4/5

The tool set adequately covers core operations like getting architecture summaries, searching symbols, classifying prompts, and retrieving twin context. Minor gaps exist, such as lacking tools to modify or create index entries, but the main read and analysis workflows are supported.

Maintenance

ActivityMaintained
ResponsivenessUnresponsive