Skip to main content
Glama

Katalog Artistov — artists for events

Карточка артиста

get_artist
Read-onlyIdempotent

Подробная карточка: описание, жанр, город, состав, репертуар и навыки, теги, фото, есть ли видео, ориентир гонорара, ссылка. Контакты не выдаются — для стоимости и свободной даты используйте форму заявки на странице карточки.

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

Input Schema

NameRequiredDescriptionDefault
urlNoИли ссылка на карточку артиста на katalog-artistov.ru
slugNoslug из search_artists

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/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 elsewhere. The description does add genuinely non-obvious behavior — contacts are withheld and pricing/availability require an out-of-band form — which is valuable. It says nothing about not-found handling or whether the optional url can fully replace the slug.

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?

Two sentences: a dense field inventory front-loaded first, then the exclusion and the alternative. The enumeration is long but every item tells the agent what it will receive, so it earns its place; only a word or two of filler.

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 field enumeration effectively substitutes for one, and the contact/fee caveat covers the main downstream expectation. The gap is the all-optional parameter set — nothing states that a url or slug must be provided, or what a miss returns.

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% and both parameters carry their own descriptions (url = link to the card, slug = slug from search_artists), so the schema does the heavy lifting. The description adds no meaning about precedence between the two or whether at least one is mandatory despite zero required parameters.

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 enumerates the concrete contents of the returned card (description, genre, city, lineup, repertoire, tags, photo, video flag, fee guidance, link), which tells an agent this is a single-artist detail retrieval, not a listing. It never names a verb like 'retrieve/get by slug' and never mentions the siblings (search_artists, list_cities, list_categories), so differentiation is only implied by the field list.

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 a clear routing rule: contacts are not returned, and fee/available-date questions must go through the request form on the card page — an explicit when-not-use plus the alternative. What is missing is guidance on pairing it with search_artists to obtain the slug, and on what to do when neither url nor slug is supplied.

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