Omega Tools MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OMEGA_ENV | No | Environment mode: 'dev' or 'production'. Defaults to 'dev'. | dev |
| OMEGA_SEARCH_MAX_RESULTS | No | Maximum number of search results to return. Defaults to 5. | 5 |
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 |
|---|---|
| omega_web_searchA | |
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 confusion or overlap. The tool's purpose is clearly defined as a web search utility.
The single tool name 'omega_web_search' follows a consistent verb_noun pattern, using snake_case and a clear prefix, establishing a consistent naming style.
Having only one tool for a server named 'Omega Tools MCP' seems very thin. While the tool itself is functional, the server's scope appears artificially narrowed, and a single tool does not justify the 'tools' plural in the name.
For the narrow domain of web search, the tool is complete. However, the server name suggests a broader suite of utilities, and the lack of any other tools (e.g., web scraping, data parsing) leaves significant gaps relative to that implied scope.