Skip to main content
Glama

Mia Amare - DJane

Search Bachata artists in Europe

kuenstler_suchen
Read-only

Directory of well-known Bachata artists active in Europe: instructor couples, DJs, singers, bands. Filters: role (instructor, dj, singer, band), country (English name), query (name, style, city).

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

Input Schema

NameRequiredDescriptionDefault
roleNoArtist role to filter by.
limitNoMaximum number of artists to return (default 30).
queryNoSearch word in artist name, style or city.
countryNoCountry name in English to filter by.

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

A3.5/5.0
Behavior3/5

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

The readOnlyHint annotation already declares this is a safe read, so the description's main added value is scope (well-known artists active in Europe) and the available filter axes. It does not state result ordering, whether filters combine with AND semantics, or what happens when no match exists; the default limit of 30 lives only in the schema.

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 compact sentence-fragment that front-loads the resource and then lists filters; there is no filler. It is slightly clipped (no verb framing such as 'Search for...'), but nothing is wasted.

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 four-parameter, all-optional read-only search with full schema coverage and no output schema, the description covers scope and filters adequately. Minor gaps: no statement of result shape or ordering, and no note that all filters are combinable.

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 coverage is 100%, so every parameter is already documented, including the role enum and the default limit. The description restates the role values and clarifies that country must be an English name and that query matches name, style or city, which is essentially duplicative of the schema rather than additive.

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 (a directory of Bachata artists active in Europe) and enumerates the entity types it covers (instructor couples, DJs, singers, bands). That makes it distinguishable in substance from a festivals or dance-school directory, though it never explicitly contrasts itself with the siblings.

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 only implied: the reader infers this is the tool for people/acts rather than events or schools. There is no explicit when-to-use statement, no exclusion, and no mention of the sibling tools that cover adjacent searches.

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