okf-tools
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 |
|---|---|
| commit_conceptC | Commit a new concept to the knowledge bundle. Creates a concept file with the given title, type, and content. Optionally checks for duplicate concepts before committing. |
| init_bundleA | Initialize a new OKF knowledge bundle at the specified path. Creates .okf/config.json, a root index.md, and updates .gitignore if in a git repo. This is the only tool that does not require a pre-configured bundle. |
| update_conceptA | Update an existing concept in the bundle. Applies only the provided fields to the concept, leaving unspecified fields unchanged. Re-embeds the content and updates the vector index. |
| move_conceptA | Move or rename a concept within the bundle. Changes the concept's location (and therefore its concept_id) without losing content, metadata, or vector-index history. Optionally updates the title in frontmatter at the same time. Examples:
|
| delete_conceptA | Delete a concept from the bundle by its concept_id. |
| show_conceptA | Show the full details of a concept by its concept_id. Returns all frontmatter fields and the complete markdown body. |
| reindexA | Rebuild the vector index for the knowledge bundle. Performs an incremental reindex by default (only processes changed files). Set full=True to discard the existing index and rebuild from scratch. Returns a JSON summary with counts of added, updated, removed, skipped concepts and the total number of indexed concepts. |
| fetch_conceptsA | Search the knowledge bundle using natural language queries. Returns a ranked list of matching concepts with scores and snippets. Supports hybrid (semantic + keyword), keyword-only, or semantic-only modes. |
| list_conceptsB | List concepts in the knowledge bundle with optional filters. Returns a filtered, sorted list of concepts. Supports filtering by type, tags, modification date, and path prefix. |
| get_statsA | Return bundle health statistics. Returns concept count, type/tag distributions, last reindex timestamp, and the number of concepts pending re-embedding. |
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 10 tools
All ten tools have distinct purposes: create, delete, search, stats, init, list, move, reindex, show, update. No overlap or ambiguity.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., commit_concept, delete_concept). Even reindex fits the pattern as a clear single action.
10 tools is ideal for a knowledge bundle manager. Each tool serves a clear purpose without being overwhelming or insufficient.
The tool surface covers the full lifecycle: init, CRUD (commit, show, list, update, delete), move, reindex, search, and stats. No obvious gaps.