ctxfw
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
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
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| prune_fileA | Extract semantic interfaces, types, pydantic models, sanitized raises, and signatures from a source file ( |
| resolve_context_bundleA | Calculate topological dependency graph distances (D0 full |
| evaluate_spec_axiomsA | Evaluate an architectural specification brief ( |
| evaluate_patchA | Verify a unified git diff patch ( |
| query_audit_ledgerA | Retrieve persisted SWE-Gate patch evaluation records and violation findings by |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
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.
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.
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.
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.