Skip to main content
Glama

Mia Amare - DJane

Find good Bachata dance schools in Europe

tanzschulen_suchen
Read-only

Selected dance schools with a strong Bachata focus in Europe, by city. Use this to answer "where can I learn Bachata in <city/country>?". Filters: city, country (English name or ISO code), query.

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

Input Schema

NameRequiredDescriptionDefault
cityNoCity name to filter by.
limitNoMaximum number of schools to return (default 30).
queryNoSearch word in school name, city or country.
countryNoCountry name (English) or ISO code to filter by.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / city / description
      Added value: +"City name to filter by."
    • addedInput schema / properties / country / description
      Added value: +"Country name (English) or ISO code to filter by."
    • addedInput schema / properties / limit / description
      Added value: +"Maximum number of schools to return (default 30)."
    • addedInput schema / properties / query / description
      Added value: +"Search word in school name, city or country."
  2. First observed

TDQS

A4/5.0
Behavior4/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 description's added value is the word 'Selected' plus 'strong Bachata focus' — that discloses the results are a curated subset rather than an exhaustive directory, which materially affects how the agent should present coverage. It does not say anything about result ordering or how many schools exist, and the result-count default lives only in the schema, but for a simple lookup tool this is solid added context.

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 sentences, with the resource/scope first and the question-template second, followed by a compact filter list. Nothing is redundant and every clause carries information the agent can act on.

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 read-only search with no output schema and full parameter documentation, the description covers the essentials: what the corpus is, what it filters on, and what question it answers. The remaining gap is that it never hints at what a returned school record contains (name, address, contact, links), which matters precisely because there is no output schema to fall back 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 all four parameters are already documented, including the 'English name or ISO code' behavior for country. The description's trailing 'Filters: city, country (English name or ISO code), query' largely restates the schema, and it omits limit entirely, adding no syntax, format, or combination semantics beyond what the schema provides.

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 and scope: 'Selected dance schools with a strong Bachata focus in Europe, by city.' An agent can immediately tell this is a curated search over dance schools, which is naturally distinct from the festival and artist siblings without needing to name them. It stops short of a clean verb-first statement (the verb is only implied, borrowed from the title), so it is clear but not maximally sharp.

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?

It gives an explicit trigger phrase — 'Use this to answer "where can I learn Bachata in <city/country>?"' — which is exactly the kind of context-plus-template that helps an agent decide to call it. There is no exclusion guidance or named alternative (e.g., when to reach for festivals_suchen or kuenstler_suchen instead), so it falls short of a 5.

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