OmniWire-MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOG_LEVEL | No | Log level (e.g., info, debug, error). | info |
| RSS_FEEDS | No | URL to a JSON configuration file or a direct JSON string of the configuration. |
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
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| fetch-newsD | – |
| check-healthD | – |
| refresh-configD | – |
| reset-sourceD | – |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| summarize-news | |
| analyze-sources |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| source-health | Real-time health status of all data sources (Sentinel Monitor) |
| news-all | Latest news items combined from all healthy sources |
| config-current | Current active configuration |
TDQS
Scored across 4 tools
Tool names suggest distinct actions: fetch-news, check-health, refresh-config, and reset-source. Some potential overlap between refresh-config and reset-source, but overall they appear to target different resources. Without descriptions, ambiguity is low but not zero.
All tools use a consistent lowercase hyphenated verb_noun pattern (fetch-news, check-health, refresh-config, reset-source). No mixing of conventions or case styles.
Four tools is a reasonable and focused set for a server. It is neither too sparse nor too large, fitting a typical small-to-medium integration.
Only four tools are exposed, covering news fetching, health check, config refresh, and source reset. Missing obvious operations like managing news items (create, update, delete) or configuration viewing, which may limit agent capabilities.