mrholmes
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MRHOLMES_OSINT_ROOT | No | Path to the OSINT workspace. If not set, the suite uses the cloned repo directory. |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| mrholmesA | Single safe utility-suite tool for the consolidated Mr.Holmes OSINT/MrHolmes Suite integration. Use action=status/catalog/run/tracker/manifest/live_test/cleanup/full_report. The run action accepts argv for mrholmes_suite.py safe commands only. |
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 1 tool
With only one tool, there is no possibility of confusing it with another tool. The agent simply selects this single tool, so disambiguation is perfect.
There is only one tool, so naming consistency is not applicable. No inconsistency exists within the tool set.
The tool count is only 1, which is too few for the apparent scope of a consolidated OSINT suite. Typically, such a suite would benefit from multiple dedicated tools rather than a single mega-tool with many actions.
The single tool exposes multiple actions (status, catalog, run, tracker, manifest, live_test, cleanup, full_report) that seem to cover a wide range of OSINT operations, suggesting good coverage for the domain.