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
check_file_impactC

Hub size and the direct callers of one file. Read decision first. high means the count is over max. Pass includeAffected only for the full module list.

check_diff_impactC

Combined blast radius and the direct callers of the changed files. Read decision first. high means the count is over max. Pass includeAffected only for the full module list.

plan_fixC

Call only when the user asked for a mechanical fix of a cycle, a layer edge, or an unused import. Writes nothing. Skip for a behavior change. Pass confirm mechanical.

architecture_statusA

Session map: primary language, top hubs, open boundaries, and the unresolved file count. Call this when impact hooks did not run or the caller set is unknown. Writes nothing.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.2/5.0

Scored across 4 tools

Disambiguation4/5

check_file_impact and check_diff_impact both analyze impact but are distinguished by scope (single file vs. changed files), and their descriptions clarify this. plan_fix and architecture_status serve clearly different purposes, though the two impact tools could still be momentarily confused.

Naming Consistency4/5

Three tools follow a verb_noun pattern (check_file_impact, check_diff_impact, plan_fix) in snake_case, while architecture_status is a noun phrase. This is a minor deviation but still readable and consistent in casing.

Tool Count4/5

Four tools are reasonable for a focused architecture impact analysis server, covering the core read-only operations without bloat. It sits at the lower end but each tool has a distinct role.

Completeness4/5

The set covers file impact, diff impact, architecture status, and mechanical fix planning, which are the core workflows. Minor gaps exist—no tool to apply a fix or inspect a specific dependency graph—but agents can work around these for the stated advisory purpose.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues