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

Tools

Functions exposed to the LLM to take actions

NameDescription
prune_fileA

Extract semantic interfaces, types, pydantic models, sanitized raises, and signatures from a source file (path) at a given pruning depth ('full', 'interface', or 'nominal') and language, optionally stripping docstrings (strip_docs), while replacing procedural bodies with AST stubs. Use this when you only need to inspect contracts or APIs of an individual dependency without ingesting raw implementation code. For multi-module dependency graphs, use resolve_context_bundle instead. Does not modify files on disk (pure in-memory AST operation).

resolve_context_bundleA

Calculate topological dependency graph distances (D0 full target_file, D1 interface stubs, D2 nominal symbols) within project_root and compile a token-pruned Markdown context bundle, with optional reactive degradation via breaker_state and session_id. Use this as your primary context builder before editing a file in a multi-module project. For inspecting isolated files, use prune_file instead. Read-only operation.

evaluate_spec_axiomsA

Evaluate an architectural specification brief (brief_text) against formal determinism rules, negative invariant floors ('never'/'shall never'), and the Axiom Completeness Index (ACI 1.0000). Use this during intake or planning phases before writing code. For verifying unified git diff patches, use evaluate_patch instead. Pure read-only analytical evaluation with no side effects.

evaluate_patchA

Verify a unified git diff patch (diff_text) against SWE-Gate architectural constraints (max_cyclomatic_delta, forbid_type_ignores, disallowed_import_modules) and functional test results (tests_passed, tests_failed, functional_verdict) before allowing merge. Appends immutable audit records (EVL-...) in SweGateStore and seals cryptographic blocks in TraceKitStore; use query_audit_ledger to retrieve or verify persisted records.

query_audit_ledgerA

Retrieve persisted SWE-Gate patch evaluation records and violation findings by evaluation_id (EVL-...), or verify and inspect cryptographic SHA-256 hash-chained audit sessions in TraceKitStore by session_id (SES-...) with optional block listing (include_blocks, max_blocks). Use this for forensic inspection and compliance verification after running evaluate_patch or context tools. Pure read-only query with zero ledger mutations.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.5/5.0

Scored across 5 tools

Disambiguation5/5

Each tool targets a clearly distinct purpose with explicit cross-references: prune_file for single-file contracts vs. resolve_context_bundle for multi-module graphs, evaluate_spec_axioms for specs vs. evaluate_patch for diffs, and query_audit_ledger for read-only forensic retrieval. No overlapping responsibilities remain ambiguous.

Naming Consistency5/5

All tool names use snake_case with a verb-first pattern (prune_file, resolve_context_bundle, evaluate_spec_axioms, evaluate_patch, query_audit_ledger). The convention is consistent throughout with no mixed styles or vague verbs.

Tool Count5/5

Five tools provide a well-scoped set covering context pruning, dependency resolution, two evaluation phases, and audit querying. Each tool earns its place without redundancy or obvious missing operations.

Completeness4/5

The surface covers the core workflow: context extraction, bundle building, spec evaluation, patch evaluation, and audit ledger querying. Minor gaps exist around explicit session/breaker management or audit initialization, but agents can work around these.

Maintenance

ActivityActive
ResponsivenessNo issues