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_fileC | Extract semantic interfaces, types, sanitized raises, and stubs from a source file. |
| resolve_context_bundleB | Calculate topological dependency distances (D0 full, D1 interface, D2 nominal) and return bundled Markdown context. |
| evaluate_spec_axiomsB | Evaluate architectural brief determinism, negative invariants floor, and Axiom Completeness Index (ACI). |
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 3 tools
Each tool occupies a distinct stage: single-file interface extraction, dependency/context resolution, and spec axiom evaluation. There is no functional overlap between them.
All three tool names follow the same verb_noun snake_case convention (prune_file, resolve_context_bundle, evaluate_spec_axioms), making the action and target of each call predictable.
Three tools is small but well-scoped for this specialized analysis server. Each tool earns its place as a necessary stage in a single coherent workflow.
The extract, resolve, evaluate pipeline covers the server's apparent read-only analysis purpose without dead ends. Minor gaps exist around batch/multi-file processing and enumeration/management of source inputs, but these are generally workable.