openhonest-umbra
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OPENAI_API_KEY | No | Enables the model layer for proof generation (CLI), or the disclosed OpenAI backend (plugin). | |
| UMBRA_JAVA_TOOLS | No | Directory holding the JDK, JaCoCo agent, and JUnit console launcher for Java audits; falls back to the repository `tools/` directory. | |
| UMBRA_OPENAI_FALLBACK | No | Set to `1` to authorize the plugin's disclosed OpenAI fallback, and only after host sampling is unavailable. | |
| UMBRA_TIMEOUT_SECONDS | No | Per-subprocess time limit for audited and generated code (default 10). | 10 |
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 |
|---|---|
| umbra_auditA | Locate test-suite blind spots in one Python, TypeScript, JavaScript, Java, Rust, or Go module and its test file. Umbra deterministically finds unexercised branches, untested input regions, unasserted return contracts, and unasserted exception paths, then reports coverage beside a transparent Silence index. It can return isolated proof requests or generate and execute failing-test proofs; the execution gate keeps only runnable tests that genuinely fail or make the audited function error. The result identifies two local report artifacts: a plain portable Markdown report and a rich, shareable, self-contained HTML visual. After it returns, write and verify a failing-test proof for each returned request, then generate both reports with module_path and tests_path only: the server includes only proofs its gate retained. Umbra proves gaps and never edits the test file. The optional OpenAI backend reads only a locally configured key after explicit confirmation; never pass a key as tool input. |
| umbra_verify_proposalA | Run one user-approved Codex proposal through Umbra's execution gate. Use proof_index from umbra_audit's structured proof_requests. Umbra retains only a runnable test that genuinely fails or makes the audited function error. It rejects malformed concrete_input or expected_property fields with a correction reason so Codex can resubmit. A passing proposal is discarded. Re-run umbra_audit after an approved test write to measure the updated suite. |
| umbra_write_reportA | After the proof loop, write both Umbra report artifacts locally with module_path and tests_path only. The persistent server automatically includes only proofs retained by umbra_verify_proposal for that same pair. retained_proofs remains an optional explicit override for compatible callers. This deterministic action re-audits locally, sends no data to any API, and does not run proof generation. |
| umbra_glossaryA | Return Umbra's authoritative fixed definition for one precise, non-standard Umbra term, or list all defined terms with short glosses. Use this whenever a user asks what an Umbra term means. Unknown terms are identified plainly and never guessed. This deterministic local tool makes no model call and sends no data anywhere. |
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 4 tools
Each tool has a completely distinct purpose: umbra_audit discovers blind spots, umbra_verify_proposal runs proposals through an execution gate, umbra_write_report generates report artifacts, and umbra_glossary defines terms. There is no functional overlap between any of these tools.
All tools share the 'umbra_' prefix and mostly follow a verb_noun pattern (audit, verify_proposal, write_report). The only deviation is umbra_glossary, which uses a noun rather than a verb, but it remains clear and predictable within the naming scheme.
With only 4 tools, the server is well-scoped for its focused purpose of test-suite auditing. Each tool serves a necessary and distinct function, and there are no redundant or superfluous entries.
The tools cover the complete workflow: audit to identify gaps, verify to test proposals, write_report to produce outputs, and glossary for reference. There are no obvious missing operations or dead ends for the stated domain.