Skip to main content
Glama

Adventskalender-Kompass

Adventskalender finden

find_calendars
Read-onlyIdempotent

Findet passende Adventskalender in der Datenbank des Adventskalender-Kompass (nur aktuell sichtbare Kalender). Alle Filter sind optional und werden kombiniert (UND); mehrere Interessen gelten als ODER, Kalender mit mehr Treffern stehen oben. Liefert höchstens 10 Kalender mit Name, Marke, Kurztext, Preisklasse, Preis pro Türchen, Zielgruppen und Link. Preisklassen: bis-20, 20-50, 50-100, ueber-100.

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

Input Schema

NameRequiredDescriptionDefault
alterNoAlter der beschenkten Person in Jahren (berücksichtigt die Altersangabe der Kalender).
limitNoAnzahl Ergebnisse, höchstens 10.
markeNoMarke oder Hersteller, z. B. "Lindt", "LEGO", "Playmobil".
veganNotrue = nur vegane Kalender.
kategorieNoInhalt, z. B. "beauty", "schokolade", "tee", "spielzeug", "lego" (Slug oder Name).
interessenNoInteressen/Stichworte, z. B. ["Star Wars", "Backen"]. Mindestens eines muss passen.
nachhaltigNotrue = nur nachhaltige Kalender.
sortierungNorelevanz (Standard: Empfehlungen zuerst), preis_aufsteigend, preis_absteigend, preis_pro_tuerchen (günstigste pro Türchen zuerst; genau mit frischem Preis, sonst geschätzt aus der Preisklasse), bewertung, neu (Ausgabe des laufenden Jahres zuerst).relevanz
zielgruppeNoFür wen? Slug oder Name, z. B. "papa", "kinder", "frauen", "oma". Untergruppen zählen mit (Kinder schließt Mädchen und Jungs ein).
alkoholfreiNotrue = nur Kalender ohne Alkohol.
preisklasseNoPreisklasse: bis 20 €, 20–50 €, 50–100 €, über 100 €.
suchbegriffNoOptionaler Freitext, alle Wörter müssen vorkommen, z. B. "Gin" oder "Harry Potter".
tuerchen_maxNoHöchstanzahl Türchen.
tuerchen_minNoMindestanzahl Türchen (meist 24).
max_preis_pro_tuerchenNoHöchstens so viel Euro pro Türchen, z. B. 1.5. Mit frischem Amazon-Preis genau, sonst nur Kalender, deren ganze Preisklasse darunter liegt.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / kategorie / description
      Previous value: -"Inhalt, z. B. \"beauty\", \"schokolade\", \"tee\", \"spielzeug\", \"lego\" (Slug oder Name, siehe list_options)."New value: +"Inhalt, z. B. \"beauty\", \"schokolade\", \"tee\", \"spielzeug\", \"lego\" (Slug oder Name)."
  2. Changed3 schema fields changed
    • addedInput schema / properties / max_preis_pro_tuerchen
      Added value: +{
      +  "description": "Höchstens so viel Euro pro Türchen, z. B. 1.5. Mit frischem Amazon-Preis genau, sonst nur Kalender, deren ganze Preisklasse darunter liegt.",
      +  "maximum": 100,
      +  "minimum": 0.1,
      +  "type": "number"
      +}
    • changedInput schema / properties / sortierung / description
      Previous value: -"relevanz (Standard: Empfehlungen zuerst), preis_aufsteigend, preis_absteigend, bewertung, neu (Ausgabe des laufenden Jahres zuerst)."New value: +"relevanz (Standard: Empfehlungen zuerst), preis_aufsteigend, preis_absteigend, preis_pro_tuerchen (günstigste pro Türchen zuerst; genau mit frischem Preis, sonst geschätzt aus der Preisklasse), bewertung, neu (Ausgabe des laufenden Jahres zuerst)."
    • changedInput schema / properties / sortierung / enum
      Previous value: -[
      -  "relevanz",
      -  "preis_aufsteigend",
      -  "preis_absteigend",
      -  "bewertung",
      -  "neu"
      -]New value: +[
      +  "relevanz",
      +  "preis_aufsteigend",
      +  "preis_absteigend",
      +  "preis_pro_tuerchen",
      +  "bewertung",
      +  "neu"
      +]
  3. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already establish readOnly, idempotent, non-destructive, closed-world behavior, so the bar is lower; the description still adds real context with the visibility constraint ("nur aktuell sichtbare Kalender"), the hard cap of 10 results, and the relevance ordering rule. It omits any note on what happens for zero matches or near-miss rankings.

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?

Three front-loaded sentences: purpose and scope first, then filter composition and ranking, then return shape and price classes. The final enumeration of price classes largely duplicates the schema enum and could be trimmed, but overall there is little waste.

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 15-parameter read tool with no output schema, the description usefully enumerates the returned fields (name, brand, short text, price class, price per door, target groups, link) and the ranking rule. The main residual gap is guidance on overlap with sibling search/lookup tools, which the description never addresses.

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 the baseline is 3, but the description adds meaning the schema does not: the AND composition across distinct filters and the OR semantics across multiple interests. The price-class enumeration is repeated from the schema enum, which is minor redundancy rather than added value.

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?

Names a specific verb and resource ("Findet passende Adventskalender in der Datenbank des Adventskalender-Kompass") and scopes it to currently visible calendars. It does not reference the available siblings (search, similar_calendars, get_calendar), so an agent must guess whether a free-text sibling is preferable for generic queries.

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?

Explains how filters compose (all optional, combined with AND, multi-value interests treated as OR) and how results are ranked ("Kalender mit mehr Treffern stehen oben"), which directly guides query construction. It stops short of saying when to use this instead of a sibling search tool or when to omit filters entirely.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources