motimate-mcp

motimate_search_learning_paths

Find learning paths in Motimate that bundle multiple trainings into a structured sequence. Filter by search term and publish status to locate published or draft learning paths.

Instructions

Sucht und listet Lernpfade in Motimate. Lernpfade bündeln mehrere Schulungen in einer strukturierten Reihenfolge.

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": "motimate_search_learning_paths"
  }
}

Input Schema

Name	Required	Description	Default
`search`	No	Suchbegriff für Lernpfade
`publish_status`	No	Status: published = veröffentlicht, draft = Entwurf

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Sep 6, 2026

TDQS

A4/5.0

Behavior3/5

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

No annotations are provided, so the description carries the behavioral burden. It clearly indicates a read-style search/list operation and explains the domain concept. However, it does not disclose result output, default behavior when no search term is supplied, or any special handling of draft learning paths.

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?

Two short sentences, front-loaded with the action and target resource. The second sentence adds useful domain context without unnecessary padding or repetition of schema details.

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 simple tool with two optional parameters, no nested objects, and no output schema, the description plus schema are sufficiently complete for correct invocation. The main gaps are the return shape and exact search semantics, but they are minor for a straightforward search/list tool.

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

Parameters3/5

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

The input schema already provides descriptions for both parameters, with 100% coverage, so the baseline is 3. The description itself adds no parameter-level details; 'search' and 'publish_status' are already adequately explained in the schema.

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 a specific operation ('Sucht und listet') on a specific resource ('Lernpfade in Motimate'), and the second sentence clarifies that learning paths bundle multiple trainings. This makes it clearly distinguishable from siblings like motimate_search_motis, motimate_search_moti_content, and motimate_get_learning_path_sections.

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 clearly implies when to use the tool: when the agent needs to search or enumerate learning paths rather than individual Motis, content, or sections. It does not explicitly name alternatives or exclusion conditions, so it stops short of a 5.

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

Deploy Server