Latzerus Lernbereich

Lernmodule durchsuchen

lernmodule_suchen

Durchsucht alle kostenlosen Lernmodule von latzerus.ch (Vertrieb, Kommunikation, KI im Arbeitsalltag, Karriere) nach Stichworten. Versteht Umschreibungen, Synonyme, Ein- und Mehrzahl sowie Tippfehler — es braucht nicht das exakte Titel-Vokabular; «Kunde will billiger» oder «Einwandbehandlung» funktionieren. Liefert Titel, Cluster, URL und Kurzbeschreibung der besten Treffer.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`maxTreffer`	No	Maximale Trefferzahl (Standard 8, max. 20)
`suchbegriff`	Yes	Stichworte oder eine Frage, z.B. 'Kunde will billiger' oder 'ChatGPT Follow-up'

Output Schema

TableJSON Schema

Name	Required	Description	Default
`anzahl`	Yes
`treffer`	Yes
`suchbegriff`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 18, 2026

changedInput schema / properties / suchbegriff / description

Previous value: -"Stichworte, z.B. 'Kaltakquise Trigger' oder 'ChatGPT Follow-up'"New value: +"Stichworte oder eine Frage, z.B. 'Kunde will billiger' oder 'ChatGPT Follow-up'"

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "anzahl": {
+      "type": "number"
+    },
+    "suchbegriff": {
+      "type": "string"
+    },
+    "treffer": {
+      "items": {
+        "properties": {
+          "beschreibung": {
+            "type": "string"
+          },
+          "cluster": {
+            "type": "string"
+          },
+          "score": {
+            "type": "number"
+          },
+          "slug": {
+            "type": "string"
+          },
+          "titel": {
+            "type": "string"
+          },
+          "url": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "slug",
+          "titel",
+          "cluster",
+          "url",
+          "score"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "suchbegriff",
+    "anzahl",
+    "treffer"
+  ],
+  "type": "object"
+}

First observedSep 16, 2026

TDQS

A4.2/5.0

Behavior4/5

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

With no annotations provided, the description carries the full burden. It transparently discloses that the tool understands paraphrases, synonyms, singular/plural forms, and typos, and that exact title vocabulary is not required. It also specifies the returned fields (title, cluster, URL, short description). This goes beyond a simple 'search' claim and sets accurate expectations for a fuzzy-matching tool.

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 two sentences, front-loaded with the primary purpose and immediately followed by the key behavioral differentiator (fuzzy matching). Every sentence earns its place—no filler, and the structure is efficient for an agent scanning for relevance.

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?

For a search tool with fuzzy matching and an output schema present, the description covers the essential inputs, the flexibility of queries, the source scope, and the output fields. It does not mention sorting or pagination behavior, but these are minor given the output schema exists and the tool's purpose is clear. The description adequately equips an agent to call it correctly.

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?

Schema description coverage is 100%, so the baseline is 3. The description adds value beyond the schema by providing concrete example queries ('Kunde will billiger', 'ChatGPT Follow-up') that illustrate the intended input semantics and the tool's tolerance for informal phrasing. This enriches the parameter understanding beyond the schema's generic description.

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 states the verb 'Durchsucht' (searches) and the specific resource 'alle kostenlosen Lernmodule von latzerus.ch' (all free learning modules from latzerus.ch). It clearly distinguishes this search tool from the sibling tools (overview, read, about) by its function of keyword-based discovery.

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?

The description implies usage when a user has keywords or a question, but it does not explicitly state when to prefer this over lernmodule_uebersicht (for listing all) or lernmodul_lesen (for reading a specific module). No exclusions or alternative routing are given, leaving usage to inference.

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

All Latzerus Lernbereich 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?