Skip to main content
Glama

Adventskalender-Kompass

Ähnliche Kalender

similar_calendars
Read-onlyIdempotent

Findet Adventskalender, die einem gegebenen ähneln (gleiche Kategorie, Zielgruppen, Interessen und Preisklasse) – etwa als Alternative, wenn einer nicht passt oder zu teuer ist.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "kalender": "<kalender>"
    },
    "name": "similar_calendars"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoAnzahl Ergebnisse, höchstens 10.
kalenderYesSlug oder Name des Ausgangskalenders.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / limit / description
      Added value: +"Anzahl Ergebnisse, höchstens 10."
  2. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, destructiveHint=false, idempotentHint and openWorldHint=false, so safety behavior is covered structurally. The description usefully defines what 'similar' means (category, target groups, interests, price range), which is real context beyond the annotations, but it says nothing about whether the source calendar itself is excluded or how results are ordered.

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?

A single front-loaded sentence with the verb and resource first, followed by a parenthetical clarification and one motivating clause. Nothing is redundant, though the parenthetical plus dash clause makes it slightly denser than strictly necessary.

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 two-parameter, closed-world read tool with full schema coverage and rich annotations, the description covers what matters: what is matched and why one would call it. Only result-set behavior (ordering, exclusion of the source item) is left unstated, and there is no output schema to lean on.

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?

Schema description coverage is 100%, so both the 'kalender' input (slug or name) and the 'limit' constraint are already documented in the schema. The description adds no syntax or format guidance for the identifier and only implicitly relates the similarity criteria to the result set. Baseline 3 applies when the schema carries the parameter documentation.

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?

States a specific verb+resource ('Findet Adventskalender') and qualifies it with the similarity dimensions (Kategorie, Zielgruppen, Interessen, Preisklasse), which distinguishes it from get_calendar or find_calendars. It does not name any sibling tool, so an agent must infer the boundary from names alone.

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?

Gives a concrete use scenario: as an alternative when a calendar 'nicht passt oder zu teuer ist'. That is clear positive context, but there is no explicit when-not guidance and no named alternative tool for the opposite case (e.g. direct search).

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