grimoire
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 | {} |
| prompts | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| grimoire_searchA | Full-text search across every indexed offline security knowledge base (HackTricks, PayloadsAllTheThings, OWASP WSTG/MASVS/ASVS, the LOTL DBs, RE/OSINT/DFIR/Bluetooth/WiFi/SDR sources, ...). Returns ranked matches with source, category, path and a snippet. Use this to ground answers and checklists in real documentation. |
| grimoire_fetch_docA | Return the full text of one indexed document (markdown, notebook converted to markdown, or extracted PDF text). Use the source+path from a grimoire_search result to read the whole page before answering. |
| grimoire_categoriesB | List the available source categories and their sources. |
| grimoire_contextA | Return the engagement context for THIS assessment: operator-declared targets/IPs, interfaces, hardware, SIM/telecom and RF parameters, plus host-detected interfaces, USB devices and SDRs. Read this first and tailor every step and command to the actual targets and hardware in scope. |
| grimoire_checklist_materialA | Gather grounded source material for a technical checklist on a topic: runs several targeted searches and returns the matching documentation snippets with citations. Feed this to build a concrete, source-backed checklist. |
| grimoire_topic_materialA | Assemble a broad reading set for a topic: runs a wide sweep of related searches across the whole corpus and returns the deduped matching docs with citations. Use this to write a complete, source-backed tutorial. Pair with grimoire_fetch_doc to read the most relevant pages in full. |
| grimoire_envA | Detect the runtime environment: whether this is an RF-Swift container, the OS and package manager, whether RF-Swift install scripts are reachable, and root/sudo availability. Use this to decide how to install tools. |
| grimoire_whichB | Check whether a tool/binary is installed and where. |
| grimoire_plan_installA | Resolve HOW a missing tool would be installed (RF-Swift script recipe first, then the host package manager) and return the ordered commands - WITHOUT running anything. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| build_checklist | Build a technical, source-backed checklist for a topic, grounded in Grimoire's indexed documentation. |
| build_tutorial | Assemble all relevant reads on a topic and synthesize a complete, source-backed pentest tutorial. |
| review_techniques | Assess whether Grimoire's indexed docs for a topic are good, current, and complete - and suggest better or newer techniques and missing coverage. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 9 tools
Each tool has a clearly distinct purpose: listing categories, gathering checklist material, returning context, detecting environment, fetching full documents, planning installation, searching, assembling topic material, and checking tool installation. There is no overlap in functionality.
All tools follow the consistent pattern 'grimoire_<descriptive_noun>', making it easy to infer their purpose from the name. The naming is predictable and uniform across the set.
With 9 tools, the server is well-scoped for a knowledge base assistant. Each tool covers a specific aspect of querying and utilizing offline security resources, without unnecessary duplication or bloat.
The tool set covers the full workflow: searching, retrieving documents, gathering material for checklists and tutorials, detecting environment, planning installations, and providing context. There are no obvious gaps for an agent to fail.