RTFM
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| rtfm_searchA | Search the indexed knowledge base. Returns ranked source paths with line ranges, no content. Use rtfm_expand to read content. |
| rtfm_coverageA | How much of a project this index actually holds. Say this before answering from the index when completeness matters: a partial index read as a complete one is how an absent result becomes "there is nothing on the subject". The denominator is the scan's own list of files — not everything in the directory. Logs, lock files, state files and build output are not counted as gaps, because RTFM was never going to index them. |
| rtfm_booksB | List indexed books with per-corpus summary and pagination. |
| rtfm_discoverA | Scan a project directory and return a structural map (file types, languages, entry points, size breakdown). ~1 second. |
| rtfm_contextA | Get sources relevant to a subject. Returns paths + line ranges, no content. Use rtfm_expand to read. |
| rtfm_expandA | Read content of an indexed file with line numbers. Use after rtfm_search. Like Read, but for indexed files. |
| rtfm_graphB | Show graph neighbors of a file (imports, links, includes, citations). |
| rtfm_historyA | Show version history of an indexed file, or retrieve a specific version. Each time a file is re-synced, its previous content is saved as a snapshot. |
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 8 tools
Most tools are clearly distinct, but rtfm_search and rtfm_context both accept a subject and return paths plus line ranges with no content, making their boundaries unclear. The descriptions do not offer a crisp rule for choosing between them, though the other six tools are easy to tell apart.
All tools share the rtfm_ prefix and use snake_case, which is good, but the pattern mixes verbs (search, discover, expand) with bare resource nouns (books, coverage, context, graph, history). A consistent verb_noun convention like rtfm_list_books or rtfm_get_coverage would be more predictable.
Eight tools is a well-scoped size for a knowledge-base/index server: enough to cover search, context, reading, exploration, coverage, history, and project discovery without feeling bloated. Each tool has a reasonable place in the workflow even if search and context could potentially be consolidated.
The server covers the core read-only workflows well: finding sources, reading content, exploring relationships, checking coverage, and viewing history. Minor gaps exist around explicit index management and book-specific operations, but most agent tasks involving querying an indexed codebase can be completed without dead ends.