OMNIA MCP
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OMNIA_LAYA_MODEL | No | Checkpoint family for the local LAYA provider (e.g., 'english', 'typed-decisions', or 'multilingual'). | |
| TYPESAFE_API_KEY | No | TypeSafe API key required when using the JEV provider. | |
| OMNIA_LAYA_DEVICE | No | Device used for local LAYA inference (e.g., 'cpu'). | |
| OMNIA_LAYA_OFFLINE | No | Set to 'true' to enable offline operation with prepared dependencies and weights for local LAYA. | |
| OMNIA_LAYA_THREADS | No | Number of threads used for local LAYA inference (e.g., '2'). | |
| OMNIA_LAYA_REVISION | No | Full revision SHA for the LAYA checkpoint (e.g., '55cf4c4ebb4ebe31b2550e8bdf3bd21b99753851'). | |
| OMNIA_DEFAULT_PROVIDER | No | The default provider to use when no provider is specified in a request (e.g., 'jev' or 'laya'). | |
| OMNIA_ALLOWED_PROVIDERS | No | Comma-separated list of providers allowed on this server (e.g., 'jev', 'laya', or 'jev,laya'). |
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 |
|---|---|
| omnia_evaluateB | Evaluate a request, persist its audit record, and expire records under retention. |
| omnia_evaluate_batchB | Evaluate a batch, persist audit records, and expire records under retention. |
| omnia_capabilitiesA | Report configured capabilities; this does not load or probe models. |
| omnia_get_decisionA | Read a persisted local decision by its opaque ID, without re-evaluating it. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| guide | Read the server's usage, provenance, and safety boundaries. |
| schemas | Read the complete public evaluation and result JSON Schemas. |
TDQS
Scored across 4 tools
The tools are mostly distinct: evaluate handles single requests, evaluate_batch handles groups, get_decision reads persisted results, and capabilities reports configuration. There is minor potential confusion between evaluate and evaluate_batch, but the descriptions clarify the difference.
Most tools follow an omnia_<verb>_<object> pattern, but omnia_capabilities is a bare noun and omnia_evaluate lacks an object, breaking the otherwise consistent style. All names share the omnia_ prefix and snake_case, so the inconsistency is moderate rather than chaotic.
Four tools is a well-scoped size for this server's purpose. Each tool covers a distinct operation—single evaluation, batch evaluation, reading decisions, and capability reporting—without unnecessary bloat.
The surface covers the core evaluation lifecycle: evaluate single, evaluate batch, and read persisted decisions, plus capability discovery. A listing or search over persisted decisions would round it out, but the existing tools support the primary workflow without dead ends.