Assurs LAMal comparator

Read comparison rules and sources

get_lamal_metadata

Read-onlyIdempotent

Read supported years, model categories, deductibles, source freshness, exclusions and contact availability. No lead is created.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_lamal_metadata"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description
`data`	No	Origin and freshness of the official data; manifest_url lists source files and the last official sync.
`models`	No	model_group codes and their meaning.
`operator`	No
`switching`	No	Switching deadline and free SPI help (cancellation, premium subsidies). Say client_sentence with the offers; a request to SPI cancels nothing by itself.
`operations`	No	URL of every operation and document.
`api_version`	No
`contact_action`	No
`deductibles_chf`	No	Accepted deductibles for child and adult.
`supported_years`	No
`accident_question`	No	Ask before quoting: employees working at least 8 hours a week for the same employer usually exclude accident cover (accident_included false).

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 25, 2026

addedOutput schema / properties / accident_question

Added value: +{
+  "description": "Ask before quoting: employees working at least 8 hours a week for the same employer usually exclude accident cover (accident_included false).",
+  "properties": {
+    "ask_before_quoting": {
+      "const": true
+    },
+    "question": {
+      "properties": {
+        "de": {
+          "type": "string"
+        },
+        "en": {
+          "type": "string"
+        },
+        "fr": {
+          "type": "string"
+        },
+        "it": {
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
+    "rule": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

addedOutput schema / properties / switching

Added value: +{
+  "description": "Switching deadline and free SPI help (cancellation, premium subsidies). Say client_sentence with the offers; a request to SPI cancels nothing by itself.",
+  "properties": {
+    "cancellation_help": {
+      "type": "string"
+    },
+    "client_sentence": {
+      "description": "Deadline, free cancellation help and free subsidy help; requested language only unless texts=all.",
+      "properties": {
+        "de": {
+          "type": "string"
+        },
+        "en": {
+          "type": "string"
+        },
+        "fr": {
+          "type": "string"
+        },
+        "it": {
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
+    "deadline": {
+      "const": "2026-11-30",
+      "description": "Date by which the cancellation must REACH the current insurer.",
+      "format": "date",
+      "type": "string"
+    },
+    "deadline_rule": {
+      "type": "string"
+    },
+    "effective": {
+      "const": "2027-01-01",
+      "format": "date",
+      "type": "string"
+    },
+    "instructions": {
+      "type": "string"
+    },
+    "request_cancels_current_insurance": {
+      "const": false
+    },
+    "subsidy_help": {
+      "type": "string"
+    },
+    "subsidy_sentence": {
+      "description": "Say it when the client mentions a modest income or asks about premium subsidies.",
+      "properties": {
+        "de": {
+          "type": "string"
+        },
+        "en": {
+          "type": "string"
+        },
+        "fr": {
+          "type": "string"
+        },
+        "it": {
+          "type": "string"
+        }
+      },
+      "type": "object"
+    }
+  },
+  "required": [
+    "deadline",
+    "effective",
+    "client_sentence"
+  ],
+  "type": "object"
+}

First observedOct 24, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the bar is lower. The description adds context annotations cannot convey: that invoking it does not create a lead, which matters in a lead-generation domain, and it enumerates the categories of data exposed (including exclusions and source freshness). It stops short of describing freshness semantics or caching behavior.

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

Conciseness4/5

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

The content is front-loaded in a single dense sentence followed by one short constraint clause, so there is no filler. The fields form a fairly long undifferentiated list, which slightly reduces scannability, but every item is informative and earns its place.

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?

With no parameters, an output schema that defines the return shape, and annotations covering safety, the description only needs to convey scope and invocation context. It does that well and adds the no-lead guarantee, though it omits any guidance on when this metadata should precede a comparison call.

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 tool takes zero parameters, so per the baseline this scores 4. The description cannot add parameter meaning because none exists, and the empty schema with additionalProperties=false is fully self-explanatory.

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

Purpose4/5

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

The verb 'Read' combines with a specific resource (LAMAL comparison metadata) and an enumerated payload: supported years, model categories, deductibles, source freshness, exclusions, contact availability. An agent knows what it retrieves, but the description never contrasts the tool with sibling comparison tools such as compare_lamal_premiums, so sibling differentiation is left implicit.

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

Usage Guidelines3/5

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

'No lead is created' implies this is a safe/free lookup compared with lead-generating siblings (request_adviser_contact, create_adviser_handoff_link), and listing metadata fields implies a pre-comparison inspection step. However, there is no explicit 'call this before X' or 'do not use this to get quotes' statement, so usage must be inferred.

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

All Assurs LAMal comparator tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?