Skip to main content
Glama
Sign In

udansa

by com.udansa
OverviewDiscussionsAdmin

Search dance events

search_dance_events
Read-onlyIdempotent

Search upcoming dance events on udansa (parties, workshops, festivals, congresses, balls) - the same results as the event search page. Filter by free text, city, dance style (any language), category, weekday, organizer and price. Recurring events appear once with their next date. Each result has id, title, style, type, city, venue, start/end, price_from (null when the organizer has not published a price; 'free' only when it really costs nothing), how tickets are sold ('udansa', 'external', 'at_the_door'), a short summary and the event page URL. Use get_event_details for tickets and programme.

Input Schema

NameRequiredDescriptionDefault
cityNoCity as listed on udansa, usually the local name ('München', 'Wien'). English names like 'Munich' are tried as well. Values: filter_options.city or get_search_filter_options.
pageNoResult page, starting at 1.
sortNo
levelNoExact level value from filter_options.level of a search result.
limitNoResults per page (1-24, default 10).
queryNoFree text, partial words allowed, e.g. 'Salsa beginners'.
styleNoDance style name in any language, e.g. 'Bachata', 'Wedding dance', 'Hochzeitstanz'. Values: filter_options.style or get_search_filter_options.
weekdayNoOnly offers on this weekday.
categoryNoExact event category from filter_options.category of a search result, e.g. 'party', 'workshop', 'festival'.
languageNoTwo-letter language code for texts, style names and page links (de, en, fr, es, it, ...). Default de.de
providerNoExact dance school or organizer name from filter_options.provider of a search result; use query for partial names.
price_maxNo
price_minNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / additionalProperties
      Added value: +false
  2. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the read-only/idempotent annotations, the description discloses important behavior: recurring events are deduplicated and shown once with their next date, and price_from has nuanced null vs 'free' semantics. It also describes ticket-sale modes and the result fields, which is valuable because no output schema exists.

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 front-loaded with the core purpose, then adds filtering, recurring-event behavior, result shape, and sibling routing. Although it is fairly long, every part carries useful information for a 13-parameter search tool with no output schema.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the absence of an output schema and the presence of 13 optional filters, the description is complete enough to call the tool correctly. It covers the main filter concepts, result fields, recurrence behavior, and the alternative for ticket/programme details, while schema-level pagination and sorting details are handled by the input schema.

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 77%, and the schema already documents most filter parameters. The description groups the filter dimensions and notes organizer and price filtering, but adds little syntax or constraint detail beyond the schema, and price_min/price_max still lack richer semantics in both places.

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 verb and resource: search upcoming dance events on udansa, with concrete event types. It also distinguishes this from get_event_details by routing detail requests to that sibling, so an agent can tell what this tool is for and what it is not.

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 gives clear filtering dimensions and explicitly points to get_event_details for tickets and programme. It does not explicitly route users to get_search_filter_options or say when not to use this tool, but the main alternative is named and the usage context is clear.

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

All udansa toolsInspect
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