Skip to main content
Glama

Katalog Artistov — artists for events

Поиск артистов

search_artists
Read-onlyIdempotent

Поиск по каталогу Каталог артистов по словам и фильтрам. Возвращает до 10 карточек: slug, имя, жанр, город, ориентир гонорара «от», есть ли видео, короткое описание, фото, ссылка. Порядок — рекомендованные каталогом, затем по популярности. Подробности — get_artist.

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

Input Schema

NameRequiredDescriptionDefault
qNoИмя или слова: «кавер-группа джаз», «фокусник», «ведущий на английском»
cityNoГород: slug или название из list_cities (артисты без города — гастролирующие — тоже попадают)
kindNosolo — сольный артист, group — коллектив
pageNoСтраница выдачи (не дальше 5-й — дальше уточняйте фильтрами)
tagsNoПодборки (slug из list_categories → tags): репертуар, язык, тип мероприятия
limitNoКарточек за вызов (до 10)
categoryNoЖанр: slug или название из list_categories
has_videoNoТолько с видео выступлений
price_maxNoБюджет на гонорар до, ₽ (артисты без указанного гонорара тоже попадают)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / category / enum
      Previous value: -[
      -  "zvezdy-estrady",
      -  "dedy-morozy",
      -  "vedushchie",
      -  "spikery",
      -  "kaver-gruppy",
      -  "vokalisty",
      -  "dzhaz-bendy",
      -  "didzhei",
      -  "saksofonisty",
      -  "skripachi",
      -  "pianisty",
      -  "muzykanty",
      -  "shou-balety",
      -  "fokusniki",
      -  "svetovye-shou",
      -  "cirkovye-shou",
      -  "barmen-shou",
      -  "pesochnoe-shou",
      -  "barabannye-shou",
      -  "sharzhisty",
      -  "aktery",
      -  "shou-programmy"
      -]New value: +[
      +  "zvezdy-estrady",
      +  "dedy-morozy",
      +  "vedushchie",
      +  "spikery",
      +  "kaver-gruppy",
      +  "vokalisty",
      +  "dzhaz-bendy",
      +  "didzhei",
      +  "saksofonisty",
      +  "skripachi",
      +  "pianisty",
      +  "muzykanty",
      +  "shou-balety",
      +  "fokusniki",
      +  "svetovye-shou",
      +  "cirkovye-shou",
      +  "barmen-shou",
      +  "pesochnoe-shou",
      +  "barabannye-shou",
      +  "sharzhisty",
      +  "aktery",
      +  "shou-programmy",
      +  "reportazhnye-fotografy",
      +  "reportazhnye-videooperatory",
      +  "detskie-animatory"
      +]
  2. Changed1 schema field changed
    • changedInput schema / properties / category / enum
      Previous value: -[
      -  "zvezdy-estrady",
      -  "dedy-morozy",
      -  "vedushchie",
      -  "kaver-gruppy",
      -  "vokalisty",
      -  "dzhaz-bendy",
      -  "didzhei",
      -  "saksofonisty",
      -  "skripachi",
      -  "pianisty",
      -  "muzykanty",
      -  "shou-balety",
      -  "fokusniki",
      -  "svetovye-shou",
      -  "cirkovye-shou",
      -  "barmen-shou",
      -  "pesochnoe-shou",
      -  "barabannye-shou",
      -  "sharzhisty",
      -  "aktery",
      -  "shou-programmy"
      -]New value: +[
      +  "zvezdy-estrady",
      +  "dedy-morozy",
      +  "vedushchie",
      +  "spikery",
      +  "kaver-gruppy",
      +  "vokalisty",
      +  "dzhaz-bendy",
      +  "didzhei",
      +  "saksofonisty",
      +  "skripachi",
      +  "pianisty",
      +  "muzykanty",
      +  "shou-balety",
      +  "fokusniki",
      +  "svetovye-shou",
      +  "cirkovye-shou",
      +  "barmen-shou",
      +  "pesochnoe-shou",
      +  "barabannye-shou",
      +  "sharzhisty",
      +  "aktery",
      +  "shou-programmy"
      +]
  3. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely new behavior: the result ordering ('рекомендованные каталогом, затем по популярности') and the concrete card shape, which an agent cannot infer from annotations. It does not discuss pagination limits beyond what the schema states.

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?

Three short sentences: purpose, return payload, ordering, then the hand-off to get_artist. The most decision-relevant facts (scope and result shape) are front-loaded and nothing is redundant.

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?

With no output schema, the description compensates by enumerating the returned fields (slug, name, genre, city, fee-from, video, description, photo, link), which is what an agent needs to trust the result. For a 9-parameter tool it leans on the very complete schema for filter semantics, leaving only minor gaps around pagination behavior and result-set completeness.

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%, including enums, ranges and usage hints (page cap, city matching touring artists, slugs from list_cities/list_categories), so the schema carries the parameter burden. The description only restates the 10-card ceiling rather than adding filter semantics, making baseline 3 appropriate.

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?

States a specific verb and resource ('Поиск по каталогу... артистов по словам и фильтрам') and bounds the result ('Возвращает до 10 карточек'). It also distinguishes itself from get_artist by deferring detail lookups there, so an agent can separate the search tool from the detail sibling without opening either schema.

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?

Clear about the search context (words + filters) and explicitly routes to get_artist for details, which is the most likely alternative an agent would confuse it with. It gives no explicit exclusions for the other siblings (list_categories/list_cities for slug discovery, request_quote for booking), so it stops short of full when/when-not guidance.

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