inquisitor
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SEARXNG_URL | No | Self-hosted SearXNG instance | |
| BRAVE_API_KEY | No | Brave Search backend (2k free/month) | |
| INQUISITOR_SESSION_DIR | No | Investigation state storage | ~/.inquisitor/sessions/ |
| INQUISITOR_DEFAULT_ENGINE | No | ddg | brave | searxng | ddg |
| INQUISITOR_SEARCH_TIMEOUT | No | HTTP timeout (seconds) | 15 |
| INQUISITOR_PREFERRED_DOMAINS | No | Comma-separated domains to boost in ranking | |
| INQUISITOR_MAX_CONTENT_LENGTH | No | Max chars per fetched page | 40000 |
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 |
|---|---|
| inquisitor_searchC | Search the web using DuckDuckGo (free), Brave, or SearXNG. |
| inquisitor_analyzeC | Scan a project directory and return a structured overview. |
| inquisitor_traceC | Trace a function, class, or method through the codebase. |
| inquisitor_scaffoldC | Set up a new project with best practices and minimal boilerplate. |
| inquisitor_phase_getB | Get the current phase of the Newton investigation. |
| inquisitor_phase_setC | Advance to a new phase in the Newton investigation process. |
| inquisitor_verifyC | Validate investigation findings against the original problem definitions. |
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 7 tools
Each tool clearly targets a distinct action: analyzing directories, searching the web, tracing code, scaffolding projects, managing investigation phases, and verifying findings. There is no overlap or ambiguity between tool purposes.
All tools follow a consistent pattern with the 'inquisitor_' prefix and snake_case verb-based names (analyze, search, trace, scaffold, phase_get, phase_set, verify). Naming is uniform and predictable.
Seven tools is well within the ideal range and each serves a distinct role in the investigation workflow. The count feels neither excessive nor sparse.
The tools cover the core investigation cycle: gather (analyze, search), understand (trace), verify, and manage progress (phase_get, phase_set). A minor gap is the lack of an explicit tool for recording or persisting findings, but the phase and verify tools partially address this.