oncallhealth-mcp
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ONCALLHEALTH_API_KEY | Yes | API key from oncallhealth.ai | |
| ONCALLHEALTH_API_URL | No | API endpoint URL (default: https://api.oncallhealth.ai) |
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
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| searchA | Search for available tools by query. Returns matching tools ranked by relevance. |
| get_schemaA | Get parameter schemas for specific tools. Use after searching to get the detail needed to call a tool. |
| executeB | Chain |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| weekly_brief | Prompt template for a weekly on-call health brief. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| methodology_resource | Provide a short methodology description. |
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose: execute chains calls, get_schema retrieves parameter details, and search finds tools. There is no overlap or ambiguity.
Tool names are imperative verbs (execute, search) and one uses get_ prefix (get_schema). While mostly consistent, the underscore in get_schema differs from the others, causing a minor deviation.
With only 3 tools, the server feels underdeveloped for the domain implied by 'oncallhealth'. The tools are generic meta-tools rather than domain-specific actions, making the count too low for its apparent scope.
The tool set is severely incomplete for an oncall health server. It lacks any domain-specific tools (e.g., managing incidents, schedules, alerts) and only provides generic utility functions, failing to cover the intended domain.