io.github.aidi1723/omniglyph
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| lookup_glyphB | Look up a single glyph in the local OmniGlyph symbol fact base. |
| lookup_termB | Look up a private or curated lexical/domain term. |
| explain_glyphC | Explain one Unicode character using the OmniGlyph Explanation Standard. |
| explain_termC | Explain a lexical/domain term using the OmniGlyph Explanation Standard. |
| explain_code_securityB | Explain Unicode source-code security findings using the OmniGlyph Explanation Standard. |
| normalize_tokensC | Normalize glyphs and known domain terms into canonical IDs. |
| list_namespacesA | List loaded lexical namespaces and their entry, alias, pack, and source summaries. |
| validate_lexicon_packB | Validate an OmniGlyph Lexicon Pack directory with pack.json and terms.csv. |
| validate_policy_packB | Validate an OmniGlyph Policy Pack directory with policy.json and intents.csv. |
| validate_output_termsC | Validate generated output terms against the local fact base. |
| enforce_grounded_outputC | Apply strict source-grounding policy to generated output terms and return allow/block decision evidence. |
| scan_code_symbolsA | Deprecated alias for scan_unicode_security. Scan source code text for suspicious Unicode symbols. |
| scan_unicode_securityA | Scan source code text for invisible Unicode controls, cross-script homoglyph risks, and other Unicode security findings. |
| scan_language_inputA | Scan natural-language input for prompt-injection directives and hidden Unicode attacks. |
| scan_output_dlpB | Scan model output for sensitive data and return redacted text. |
| enforce_intentA | Apply an intent sandbox manifest and return allow, review, or block without executing commands. |
| audit_explainC | Return an OES explanation together with an audit event showing actor, sources, and unknowns. |
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 17 tools
Each tool targets a distinct function: explanation, normalization, listing, validation, scanning, enforcement, lookup, and audit. The only potential overlap is the deprecated scan_code_symbols, but its description clarifies it as an alias for scan_unicode_security. All other tools have clearly separated purposes.
All tool names follow a consistent verb_noun pattern with underscores, such as explain_term, scan_unicode_security, lookup_glyph, and enforce_intent. The pattern is uniform across the set, with no mixing of conventions or irregular cases.
With 17 tools, the count is slightly above the typical 3-15 range but still reasonable for the domain. Each tool serves a specific purpose, and none feel redundant. The scope of OmniGlyph justifies the number.
The tool set covers explanation, normalization, validation, scanning (security, input, output), enforcement, lookup, and auditing. While it lacks tools for creating or editing lexicon/policy packs, the focus on validation and scanning is well-covered. No critical gaps are apparent for the stated purpose.