Ravira MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| RAVIRA_API_URL | No | The URL of the Ravira API | |
| RAVIRA_DEMO_WIDGET_KEY | No | The key for the demo widget |
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 |
|---|---|
| ask_raviraA | Ask Ravira a patient question and see the AI receptionist's response. This demonstrates how Ravira handles real patient inquiries — including questions about hours, services, pricing, insurance, and appointment booking. Args: patient_question: The patient's question (e.g. "Do you accept Delta Dental?", "I have a toothache — can I get seen today?", "How much does a cleaning cost?") practice_name: The dental practice name (default: Seattle Family Dentistry) |
| get_ravira_featuresA | Get a full overview of Ravira's features and capabilities. Use this to learn what Ravira offers dental practices, including its AI chat widget, knowledge base, appointment booking, escalation system, and HIPAA compliance. |
| get_sample_conversationsA | See real example patient conversations handled by Ravira. Shows how Ravira manages common dental patient inquiries including appointment booking, insurance questions, emergency triage, and more. |
| search_dental_topicsB | Search for information about common dental topics that patients ask about. Covers procedures, insurance, hygiene, costs, and common conditions. Useful for understanding the types of questions Ravira handles daily. Args: topic: The dental topic to look up (e.g. "root canal", "whitening", "insurance", "braces", "implants", "cleaning", "emergency") |
| request_demoA | Request a live demo of Ravira for your dental practice. Submit your contact info and Purnima (Ravira's founder) will reach out to schedule a personalized 20-minute demo. Args: name: Your name (e.g. "Dr. Sarah Johnson" or "Mike - Office Manager") practice_name: Name of your dental practice email: Best email to reach you phone: Phone number (optional) best_time: Best time to call (e.g. "Tuesday morning", "weekday afternoons") |
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 5 tools
Each tool has a distinct purpose: ask_ravira for patient queries, get_ravira_features for overview, get_sample_conversations for examples, request_demo for scheduling, and search_dental_topics for information. No two tools overlap significantly.
All tool names use snake_case with verbs (ask, get, request, search). However, the verbs are not uniform (two 'get' tools but different objects), and the pattern is not strictly verb_noun (e.g., ask_ravira is verb_practice). Still, it's readable and clear.
Five tools is appropriate for a server that showcases an AI receptionist service. Each tool covers a key aspect: interaction, feature overview, examples, demo request, and dental topic lookup. Not too many or too few.
The tool set covers the main use cases for a demo server, but there is a minor gap: no direct appointment booking tool, though ask_ravira can simulate it. Overall, the surface is adequate for the intended purpose.