headcleaner
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 | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_chunksC | Return cited, policy-gated chunks from an existing local bundle index. |
| get_chunkC | Return one cited chunk after root, policy, and index validation. |
| get_diagnosticsB | Return a stable, content-free diagnostics envelope for a local bundle. |
| get_readinessC | Return a stable, content-free readiness envelope for a local bundle. |
| list_review_queueC | Return a stable, content-free review-queue envelope for a local bundle. |
| okf_list_bundles_toolA | List the OKF bundles this server has loaded. |
| okf_search_toolB | Search one or all loaded bundles. |
| okf_get_concept_toolA | Read one concept (frontmatter + body). Accepts id, title, or filename stem. |
| okf_context_toolC | Assemble legacy graph context and an additive indexed package when available. |
| okf_related_toolC | Top-k concepts by link degree (inbound + outbound count). |
| okf_impact_toolB | Report outbound / inbound / transitive links for a concept. |
| okf_doctor_toolB | Health report for a bundle (score, errors, warnings, per-rule findings). |
| okf_diff_toolC | What changed on disk since the bundle was loaded. |
| okf_refresh_toolC | Re-ingest a bundle so the in-memory catalog reflects current files. |
| okf_sql_toolA | Read-only SELECT over the in-memory catalog (concepts, links). |
| okf_registry_listA | List all bundles registered under @slug aliases. |
| okf_registry_addB | Add a bundle under a slug alias. Then reference it as @/... . |
| okf_registry_removeB | Remove a slug from the registry. |
| okf_registry_resolveA | Resolve |
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 19 tools
Several tool groups are hard to distinguish: okf_related_tool vs okf_impact_tool both analyze links, search_chunks vs okf_search_tool both search, and okf_doctor_tool/get_diagnostics/get_readiness/list_review_queue all sound like status/health endpoints. The descriptions help only after close reading, but an agent could easily pick the wrong tool.
Naming conventions are mixed: some tools use okf_*_tool, some use bare get_*/list_* verbs, and registry tools use okf_registry_*. There is no consistent verb_noun or prefix/suffix rule across the set.
19 tools is on the heavy side; many are justified by the range of bundle, registry, search, SQL, and graph-analysis capabilities, but the status-envelope and search/link-analysis overlaps add bulk. It is not egregiously overpopulated, but it exceeds the comfortable 3-15 range.
The server covers the main read-side lifecycle: list/load bundles, search/read concepts and chunks, inspect health/diff, manage registry aliases, and run SQL. Missing mutation tools for bundle content and review actions are likely out of scope, forming only minor gaps agents can work around.