Skip to main content
Glama

search_wlo_collections

Find curated educational topic pages (Sammlungen) on WirLernenOnline by subject, level, or audience. Retrieve nodeIds for accessing collections' content.

Instructions

Search WirLernenOnline (WLO) for Sammlungen (= Themenseiten). In WLO, a "Sammlung" is the same as a "Themenseite": a curated thematic page that bundles educational content items in swimlanes (Schwimmlinien/Karussells) grouped by topic, subject or level. Users may ask for "Themenseite Algebra", "Sammlung Klimawandel" or "Portal Mathematik" – these all refer to collections. Use the returned nodeId with get_collection_contents to retrieve the actual content items. Filters accept both German labels (e.g. "Mathematik", "Grundschule", "Lehrer/in") and full URIs.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryNoSearch query in German, e.g. "Klimawandel" or "Algebra". Leave empty to browse top-level collections.
userRoleNoTarget audience (Zielgruppe): e.g. "Lehrer/in", "Lerner/in", "Eltern", or URI
disciplineNoSubject (Fach/Schulfach): e.g. "Mathematik", "Biologie", "Informatik", or URI
maxResultsNoMaximum number of results (1–20, default 5)
outputFormatNo"markdown" (default, human-readable) or "json" (structured)markdown
parentNodeIdNoNodeId of a parent collection to search within (e.g. Mathematik nodeId to find "Algebra" inside it). Leave empty to search from the WLO root. Returned by a previous search_wlo_collections call.
excludeNodeIdsNoSkip these node IDs in the result (already-seen items, e.g. for paginated drill-downs)
educationalContextNoEducational level (Bildungsstufe): e.g. "Primarstufe", "Sekundarstufe I", "Hochschule", or URI
Behavior3/5

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

No annotations are present, so the description carries the full burden. It discloses domain semantics, synonym coverage, and filter input flexibility (labels and URIs), and hints at follow-up behavior. However, it does not describe result ordering, pagination, or what happens with empty queries beyond a parameter note, leaving gaps in behavioral expectations.

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 succinct: four sentences cover purpose, domain equivalence, workflow, and filter encoding. Every sentence earns its place with no redundancy or padding.

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 8 optional parameters and no output schema, the description gives the essential workflow (search → nodeId → get_collection_contents) and domain clarifications. It does not explain the return structure or the markdown/json outputFormat behavior, but the schema covers the parameter details. Reasonably complete for a search tool.

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 coverage is 100%, so baseline is 3. The description adds cross-cutting parameter semantics: all filters accept both German labels and full URIs, and it explains the query parameter's German focus. This is meaningful beyond the individual schema descriptions, which mostly give examples and defaults.

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 opens with 'Search WirLernenOnline (WLO) for Sammlungen (= Themenseiten)', a specific verb+resource. It clarifies that Sammlung equals Themenseite and lists synonyms ('Themenseite Algebra', 'Sammlung Klimawandel', 'Portal Mathematik'), effectively distinguishing this from content search by directing to get_collection_contents.

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 provides clear usage cues: when users ask for Themenseite/Sammlung/Portal, this is the tool. It also gives a workflow ('Use the returned nodeId with get_collection_contents'). However, it does not explicitly contrast with sibling search tools like search_wlo_topic_pages or search_wlo_content, missing an opportunity for exclusion guidance.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/janschachtschabel/wlo-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server