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.

Deterministic Context Firewall & Sovereign Pentad Verification Workflow:

  1. Architectural Intake: Call evaluate_spec_axioms on architectural briefs to verify determinism and negative invariants (ACI >= 0.9000).

  2. Context Assembly: Call resolve_context_bundle for multi-module topological dependency bundles (D0/D1/D2/D3) or prune_file for single-file AST interface extraction.

  3. Pre-Merge Verification: Call evaluate_patch on unified git diffs to enforce cyclomatic complexity budgets, type-ignore bans, import restrictions, and functional test gates.

  4. Forensic Audit Retrieval: Call query_audit_ledger to inspect persisted SWE-Gate evaluation records (EVL-...) or verify cryptographic SHA-256 hash-chained sessions (SES-...).

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' retains full AST with sanitized raises, 'interface' replaces procedural bodies with ... stubs [default], or 'nominal' retains top-level symbol declarations only) and language ('python' [default], 'typescript', 'javascript', 'go', 'java'), optionally stripping docstrings (strip_docs, default false). 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.

resolve_context_bundleA

Calculate topological dependency graph distances (D0 full target_file, D1 interface stubs, D2 nominal symbols) within project_root (defaults to target_file's parent directory) and compile a token-pruned Markdown context bundle, with optional reactive degradation via breaker_state ('CLOSED', 'TRIPPED' strips D2+ modules, or 'HALTED' compacts D1 to nominal stubs) and session_id ('SES-...' linked to TokenCast budget tracking). Use this as your primary context builder before editing a file in a multi-module project; for inspecting isolated files, use prune_file instead.

evaluate_spec_axiomsA

Evaluate an architectural specification brief (brief_text) against formal determinism rules, requiring at least 5 explicit negative invariants ('never' or 'shall never'), bounded variable domains, deterministic finite-state machine (FSM) transitions, and a 4-class error taxonomy to reach VERIFIED status (aci_score >= 0.9000 and SHA-256 manifest_hash; otherwise QUARANTINED with remediation notes). Use this during intake or planning phases before writing code; for verifying unified git diff patches, use evaluate_patch instead.

evaluate_patchA

Verify a unified git diff patch (diff_text, with optional commit_sha, author_kind 'AGENT'|'HUMAN', pr_id, diff_size_bytes, repo_name, and repo_id) against SWE-Gate architectural constraints (max_cyclomatic_delta default 10, forbid_type_ignores default true, disallowed_import_modules) and functional test results (tests_passed default 1, tests_failed default 0, functional_verdict 'PASSED'|'FAILED') 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-<16 lowercase hex chars>), or verify cryptographic SHA-256 hash-chained audit sessions in TraceKitStore by session_id (SES-...) with optional block pagination (include_blocks default true, max_blocks 1..256 default 50); at least one of evaluation_id or session_id must be provided. Use this for forensic inspection and compliance verification after running evaluate_patch or context tools.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.4/5.0

Scored across 5 tools

Disambiguation5/5

Each tool targets a distinct operation: single-file pruning, multi-module bundle compilation, spec evaluation, patch evaluation, and audit retrieval. Descriptions explicitly disambiguate boundaries, e.g. prune_file says 'for multi-module dependency graphs, use resolve_context_bundle instead' and evaluate_spec_axioms points to evaluate_patch for diffs.

Naming Consistency5/5

All five tools use snake_case with a leading verb (prune_file, resolve_context_bundle, evaluate_spec_axioms, evaluate_patch, query_audit_ledger). The verb_noun pattern is predictable and the two evaluate_* tools share a consistent prefix for their judgment family.

Tool Count5/5

Five tools is well-scoped for a context-bundling and verification framework: two for context generation, two for evaluation gates, one for audit. No tool looks redundant and none of the sub-capabilities appear padded.

Completeness4/5

The prune/bundle, spec-evaluate, patch-evaluate, and audit-query lifecycle forms a coherent closed loop, but session management is an implicit dependency: session_id (SES-...) is consumed as input with no tool to create or list sessions, and TokenCast budget state is referenced but never exposed.

Maintenance

ActivityActive
ResponsivenessNo recent community issues