Skip to main content
Glama

Mia Amare - DJane

Search Bachata festivals in Europe

festivals_suchen
Read-only

Upcoming Bachata festivals, congresses and weekenders in Europe (next 12 months), chronological. Optional filters: month (YYYY-MM), country (ISO code, e.g. ES, DE), query (name or city), limit.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
monthNoYYYY-MM
queryNo
countryNoISO 3166-1 alpha-2

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

readOnlyHint=true already tells the agent this is a safe read, so the bar is lower. The description still adds useful behavior: a bounded 12-month forward window and chronological ordering of results. It does not mention defaults (e.g. limit when unspecified) or whether results are capped/paginated, which is the remaining behavioral gap.

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 tight sentences: scope and ordering are front-loaded, then the optional filters are enumerated in a compact list. Nothing is redundant or buried.

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 read-only search with four optional parameters and no output schema, the definition covers scope, ordering and all filter meanings adequately. It stops short of stating the default limit and the exact sort direction, which an agent would want before relying on result shape.

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 only 50%, and the description compensates for the weakest part: query is documented as 'name or city' (the schema gives it no description at all), and country gains concrete examples (ES, DE) beyond the bare ISO reference. Month's YYYY-MM format is merely repeated from the schema, and limit's default is still unstated, keeping it below a 5.

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?

The description names a specific resource (Bachata festivals, congresses, weekenders), a geographic scope (Europe) and a time horizon (next 12 months), plus ordering (chronological). It is clearly distinguishable from siblings like kuenstler_suchen or tanzschulen_suchen by resource type, though it never explicitly contrasts itself with them.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by the framing ('upcoming ... festivals ... Optional filters'), so an agent can infer this is the lookup for festival events. There is no explicit statement of when to prefer it over a sibling, no exclusions, and no note on what happens when filters are omitted.

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