Swiss Health MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SUPABASE_URL | Yes | The URL of your Supabase project (e.g., https://YOUR_PROJECT.supabase.co) | |
| SUPABASE_SERVICE_ROLE_KEY | Yes | Your Supabase service role key |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_cheapest_insurersC | Findet die günstigsten Krankenkassen für ein bestimmtes Profil. Gibt die Top 5 zurück. |
| compare_insurersC | Vergleicht mehrere Versicherer für ein bestimmtes Profil. |
| get_price_historyC | Zeigt die Preisentwicklung eines Versicherers über mehrere Jahre. |
| get_database_statsB | Zeigt Statistiken zur Datenbank (Anzahl Einträge, verfügbare Jahre, Versicherer). |
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 4 tools
The tools have mostly distinct purposes: compare_insurers compares multiple insurers, get_cheapest_insurers finds the cheapest ones, get_database_stats shows database statistics, and get_price_history shows price trends. However, compare_insurers and get_cheapest_insurers could potentially overlap in function if comparing insurers includes price considerations, but their descriptions clarify distinct focuses (comparison vs. cheapest selection).
All tool names follow a consistent verb_noun pattern in snake_case: compare_insurers, get_cheapest_insurers, get_database_stats, and get_price_history. This uniformity makes the set predictable and easy to understand, with no deviations in naming conventions.
With 4 tools, the count is borderline for a health insurance domain. It feels slightly thin as it covers comparison, cheapest selection, stats, and price history, but lacks tools for detailed insurer information, plan specifics, or user profile management, which might be expected in a comprehensive health insurance server.
The tool set covers key aspects like comparison, cost analysis, stats, and history, but has notable gaps. For a health insurance domain, missing operations include creating or updating profiles, retrieving detailed insurer data, or managing user preferences, which could limit agent effectiveness in broader workflows.