Skip to main content
Glama

Search artists

search_artists
Read-onlyIdempotent

DJs and live acts listed on Lineup Atlas, by name or genre, optionally only those playing in a 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": "search_artists"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityNoOnly artists with an upcoming date in this city.
limitNoHow many results (1 to 20, default 10).
queryNoAn artist name or a genre.
localeNoLanguage of the texts and page links (default: en).

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 readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so safety is fully covered by structured data. The description adds only the scope statement that results come from the Lineup Atlas artist catalog and can be city-filtered, with no added detail on result ordering, pagination, or empty-query behavior.

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?

A single front-loaded sentence fragment with no filler; the resource is stated first and the narrowing filters follow, so nothing needs trimming and nothing is 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 read-only, zero-required-parameter search with full schema coverage and no output schema, the definition covers the essentials: resource scope plus the two filtering axes. It stops short of describing default behavior when no query is supplied, which would matter for an agent calling it bare.

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 every parameter including the locale enum and the 1-20 limit is already documented. The description echoes the name/genre and city semantics but adds no syntax hints or edge-case meaning beyond the schema, so the baseline 3 applies.

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 concrete resource (DJs and live acts on Lineup Atlas) and the two search modes (by name or genre, optionally scoped to a city), which lets an agent distinguish it from siblings like search_events and search_venues. The search verb itself is only implied by the tool name and title rather than stated, which keeps it just short of a 5.

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: use it when you want artists by name or genre, and add a city to narrow to artists with upcoming dates there. There is no explicit when-not-to-use guidance, no routing to get_artist_dates for a known artist's schedule, and no mention of what happens when query is 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