Skip to main content
Glama
sluyasu

Insurance Wiki MCP Server

by sluyasu

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

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

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
list_countriesA

List countries covered: product/insurer/regulation counts, how many branches have at least one product (branches_covered), the size of the country's branch taxonomy (branch_taxonomy), and how many hand-written branch overview pages exist (branch_overview_pages).

list_branchesA

List insurance branches for a country with their labels, mandatory flag and product counts.

searchA

Search wiki pages by title/branch/insurer and page content. Filter by type (product|branch|insurer|regulation|concept|moc), branch slug, insurer slug. Returns matches with path, source_url and freshness; when more than limit pages match, the response says how many were left out.

get_pageA

Return the full text of one knowledge page by its repo-relative path (from search results). Text files in the knowledge folders only (.md, .json, .yml, .yaml, .txt, .csv).

get_productA

Return a product's structured data (coverages, exclusions, deductibles, etc.) as JSON, plus its source_url. product_name is matched case-insensitively (substring). Optional filters: document_type (conditions_generales | ipid | conditions_particulieres | conditions_tarifaires) and edition (substring of the edition_date, e.g. '2026'). When one product has several documents (e.g. its CG and its IPID share the commercial name), the general conditions with the newest edition are returned and the other documents are listed under other_documents.

get_coverageA

Compact, question-oriented view of ONE product: only the coverages and exclusions relevant to topic (e.g. 'vol', 'degats des eaux', 'ski hors-piste'), with their limits, deductibles, verbatim quotes and page numbers. Prefer this over get_product when answering a specific guarantee question: everything needed to quote is in the response and nothing else. Matching is accent- and case-insensitive over coverage/exclusion names and descriptions. An empty match list means the topic was not found in THIS document; that is not proof the product has no such cover - say so and point to the source_url.

verify_claimA

Verbatim evidence check for ONE factual claim about a product ('le ski hors-piste est couvert avec un moniteur', 'franchise de 250 EUR en vol'). Returns the document excerpts (coverages, exclusions, quotes, definitions, deductibles, summary) sharing the claim's terms, each with its page when stated. The tool does NOT judge: compare the claim against the excerpts. If a number, date, article or condition the claim relies on appears in no excerpt, treat it as NOT SUPPORTED by this document and say so. Use it as a self-check before asserting product facts to a user.

compare_productsA

Compare 2+ products side by side on one dimension: coverages | exclusions | deductibles. Each name is matched case-insensitively against extracted product names; pass insurer_slugs (same length/order as product_names) to pin each name to one insurer. A name matching several DISTINCT products is refused with the candidates listed (refine it rather than let the server guess). For each resolved name the best document is selected (general conditions over IPID, newest edition) and identified in the response, including its superseded flag.

find_overlapA

Flag CANDIDATE duplicate cover when combining 2+ products (e.g. a home policy + a family-liability policy). Each product's coverages (or exclusions) are tagged with a controlled category (schema/coverage_categories.json); a candidate overlap is a category present in 2+ of the products. Deterministic + heuristic: it surfaces likely duplicates for an agent to confirm against the actual descriptions. It does not advise or rank, and can miss overlaps the taxonomy doesn't yet cover. Pass insurer_slugs (same length/order as product_names) to pin each name to one insurer; the best document per name is selected (general conditions over IPID, newest edition).

get_branch_overviewB

Return the hand-authored overview page for a branch (by slug or label).

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4/5.0

Scored across 10 tools

Disambiguation5/5

Each tool targets a distinct operation: navigation (list_countries, list_branches), retrieval (get_branch_overview, get_page, get_product), focused coverage lookup (get_coverage), claim verification (verify_claim), comparison (compare_products), and overlap detection (find_overlap). Even where tools operate on similar data (products/coverages), their purposes are clearly differentiated.

Naming Consistency5/5

All tool names follow a consistent verb-first pattern: 'list_' for enumeration, 'get_' for retrieval, and specific action verbs for other operations (search, verify, compare, find). The naming is uniform and predictable across the set.

Tool Count5/5

10 tools is well-scoped for an insurance knowledge server. Each tool provides a distinct capability without redundancy or fragmentation, covering browsing, searching, retrieving, verifying, comparing, and analyzing insurance data.

Completeness4/5

The tool set covers the core lifecycle of querying insurance wiki data: navigation, search, retrieval, product details, coverage queries, claim verification, and comparison. Minor gaps exist (e.g., no direct list_insurers or list_regulations), but the search tool with filters compensates for these adequately.

Maintenance

ActivitySlowing
ResponsivenessUnresponsive