Skip to main content
Glama

get_ravira_features

Get a full overview of Ravira's dental practice features, including AI chat widget, knowledge base, appointment booking, escalation system, and HIPAA compliance.

Instructions

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.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The `get_ravira_features()` function (decorated with @mcp.tool()) is the handler for the 'get_ravira_features' tool. It returns a long markdown string describing Ravira's features including AI Chat Widget, Smart Knowledge Base, Appointment Booking, Escalation System, Conversations Dashboard, HIPAA Compliance, and Multi-Practice support.
    def get_ravira_features() -> str:
        """
        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.
        """
        return """
    # Ravira — AI Receptionist for Dental Practices
    
    ## What Ravira Does
    Ravira is a 24/7 AI-powered front desk assistant that embeds directly on a
    dental practice's website. It answers patient questions instantly, collects
    appointment requests, and flags anything it can't handle for staff.
    
    ---
    
    ## Core Features
    
    ### 1. 24/7 AI Chat Widget
    - Embeds on any dental website with a single line of code
    - Patients get instant answers even after hours
    - Handles unlimited simultaneous conversations
    - Mobile-friendly design
    
    ### 2. Smart Knowledge Base (RAG)
    - The AI answers ONLY from the practice's own content — no hallucinations
    - Staff can add, edit, or delete knowledge base entries anytime
    - Auto-import from website: paste a URL and Ravira builds the KB automatically
    - Covers: hours, services, pricing, insurance, policies, staff bios
    
    ### 3. Appointment Booking
    - AI collects patient name, preferred date/time, and service type
    - Appointments appear instantly in the staff dashboard
    - Staff can confirm, reschedule, or cancel with one click
    - Filter by status: pending / confirmed / cancelled
    
    ### 4. Escalation System
    - When the AI can't handle a question, it flags it for staff immediately
    - Dashboard shows all escalations with status tracking
    - Ensures no patient falls through the cracks
    - Escalations marked: pending → acknowledged → resolved
    
    ### 5. Conversations Dashboard
    - Staff see all patient chats in one place
    - Searchable conversation history
    - See what patients ask most — informs knowledge base improvements
    
    ### 6. HIPAA-Compliant by Design
    - Patient message content stored in memory only — never in the database
    - Sessions auto-expire after 2 hours of inactivity
    - Only anonymized metadata stored (intent, character count)
    - Full audit logging middleware built in
    
    ### 7. Multi-Practice / Multi-Tenant
    - Each dental practice has its own secure login
    - Data fully isolated per practice
    - Knowledge base is practice-specific
    
    ---
    
    ## Coming Soon
    - SMS channel (text message support)
    - Voice channel (phone call AI)
    - Stripe billing integration
    - EHR/PMS integrations (Dentrix, Eaglesoft)
    
    ---
    
    ## Ideal For
    - Solo dentists (1 provider) overwhelmed by front desk calls
    - Small group practices (2-3 providers) with limited admin staff
    - Any practice losing patients to unanswered after-hours calls
    
    ---
    
    ## Pricing
    Contact Purnima for pilot pricing: ravira.ai
    Currently offering FREE 60-day pilots to Seattle-area practices.
    """
  • server.py:163-164 (registration)
    The `@mcp.tool()` decorator on line 163 is the registration mechanism — it registers `get_ravira_features` as a tool with the FastMCP server instance.
    @mcp.tool()
    def get_ravira_features() -> str:
  • The docstring and signature serve as the schema — the function takes no parameters and returns a string. The docstring describes the tool's purpose, which the FastMCP framework uses for tool description/introspection.
    """
    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.
    """
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description must handle behavioral disclosure. It implies a read-only operation by being a 'get', but does not explicitly state that it has no side effects, requires no authentication, or any other behavioral traits.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise with two sentences that front-load the primary purpose immediately. Every sentence adds value, with no redundant or vague phrases.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given zero parameters and an existing output schema, the description adequately lists key features returned. It could be more precise about the structure of the output, but it provides enough context for an agent to decide when to use this tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has zero parameters, and schema description coverage is 100%. The description adds value by specifying what the overview includes (e.g., features, HIPAA compliance), which is beyond the empty schema. Baseline for high coverage is 3, but the additional context warrants a 4.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb 'Get' and the resource 'full overview of Ravira's features and capabilities'. It lists specific features (AI chat widget, knowledge base, etc.), making the purpose distinct from sibling tools like ask_ravira or search_dental_topics.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly says 'Use this to learn what Ravira offers', providing clear context. It doesn't mention when not to use or alternatives, but the absence of parameters and the overview nature make it self-evident.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/pvijaya645/ravira-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server