Ringback
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PYTHON_BIN | No | Python that has pjsua2 (auto-detected) | |
| VOICE_SIP_ID | Yes | Your SIP address, e.g. sip:you@sip.linphone.org | |
| PJPROJECT_DIR | No | pjsua2 build dir (auto-detected) | |
| WHISPER_MODEL | No | STT model: base.en (fast) · small.en (default) · medium.en (accurate) | |
| OPENSSL_PREFIX | No | OpenSSL libs (auto-detected) | |
| VOICE_SIP_PASS | Yes | Your SIP password | |
| VOICE_SIP_USER | Yes | SIP username (the part before @) | |
| VOICE_SIP_PROXY | No | SIP registrar/proxy | |
| VOICE_SIP_CALLEE | No | Address to call (normally yourself) |
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 |
|---|---|
| alert_meA | Physically buzz the user's phone with an urgent push notification. The user is NOT watching the screen. Calling this interrupts them in the real world, so use it only when that interruption is justified. USE FOR:
DO NOT USE FOR:
Args: message: One-sentence body, shown on the lock screen. Be specific and actionable, e.g. "QA deploy failed: migration 0042 errored on playground_management" — not "something went wrong". severity: "info" | "warn" | "critical". - "critical" = loudest + most intrusive. May place a ringing phone call (SIP / Linphone — full-screen, pierces silent) and/or a Pushover emergency alert that repeats until acknowledged. Reserve for things that genuinely must interrupt the user right now. - "warn" (default) = high-priority push, non-repeating, no call. - "info" = normal-priority push, no call. title: Short notification title (a few words). Returns a status string describing what each backend did. |
| alert_testA | Send a low-priority TEST notification to verify connectivity. Safe to call during setup: it always uses 'info' severity so it will not fire a loud or repeating critical alert. Use this to confirm the phone receives pushes before relying on alert_me for real conditions. |
| alert_statusA | Report which alert channels are configured (no secrets revealed). Useful for debugging setup: shows the active channel, whether each backend has its credentials, and the current rate-limit settings. |
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 3 tools
Each tool has a clearly distinct purpose: alert_me sends real alerts, alert_status checks configuration, and alert_test sends a test notification. There is no overlap or ambiguity.
All tool names follow a consistent verb_noun pattern (alert_me, alert_status, alert_test) with underscores, making them predictable and easy to understand.
With only 3 tools, the server is well-scoped for its purpose of sending alerts and checking status. Each tool earns its place, and the count is within the ideal 3-15 range.
The server covers the core operations: sending alerts, checking configuration, and testing connectivity. While missing features like alert history or cancellation, it provides a complete surface for its stated purpose.