Omega API MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OMEGA_API_KEY | Yes | Your Omega-API key (oapi_live_...). Register at https://omega.dailui.com/signup.php to get one. |
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 |
|---|---|
| omega_judge_turnA | Judge one agent turn: does the conversational process move? Returns a decision and a gate action. Measures process shape, not whether the goal was reached. Act on the gate before showing the reply: release -> show; clarify -> regenerate then call again; suppress -> stop or escalate; none -> observe only, show. |
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 overlap or confusion. The tool's purpose is clearly specified and distinct by default.
The single tool name 'omega_judge_turn' follows a clear verb-object pattern and is internally consistent. There is no other tool to conflict with.
The server has only one tool, which feels thin for a general-purpose API server. While the tool is well-scoped, the count is borderline per the calibration guidelines.
Within the narrow domain of judging agent turns, the tool provides a complete lifecycle: it evaluates a turn and returns a decision with the necessary gate action. No obvious dead ends or missing operations are apparent.