Umbra
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| scan_repoA | Scan a repository and return the full Umbra Trust Score report as JSON (SAFE/CLEAN static findings; deep=true also verifies RUNS and HONEST in a Docker sandbox). Call before declaring a task done — a score below 50 means the work is not done. |
| guard_contentA | Check a proposed file write against the Umbra guard engine BEFORE writing. Returns the guard verdict as JSON: decision (allow/warn/block), findings with file:line evidence, and pathViolation when a protected path (e.g. .git/hooks) is targeted. On block, do not write — fix the content and re-check. |
| get_scoreA | Fast static Umbra Trust Score (0-100) for a repository — SAFE and CLEAN axes only, no network, no sandbox. Use scan_repo for the full report with findings. |
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 3 tools
scan_repo and get_score both assess repository trust, but scan_repo provides a comprehensive report with findings while get_score is a fast static-only subset, making them distinguishable. guard_content is clearly distinct for write-time guarding.
All tool names follow the verb_noun snake_case pattern (scan_repo, get_score, guard_content), which is consistent and predictable.
Three tools is appropriate for the focused domain of repository trust scoring and content guarding; each tool has a clear purpose.
The set covers the main workflows: full scanning, quick scoring, and pre-write content guarding. Minor gaps exist, such as no explicit tool for retrieving historical reports or updating guard rules, but agents can work around these.