Skip to main content
Glama

Search Performers

search_performers
Read-only

Find a performer (artist, team or comedian) on XP by name, with optional genre or sport filters -- 'Phish', 'the Lakers'. Returns performer cards, not events; search_events with the performer's name returns their upcoming events.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "search_performers"
  }
}

Input Schema

NameRequiredDescriptionDefault
genreNoOptional genre filter.
limitNoMax performers to return.
queryYesNatural language performer search query.
sportNoOptional sport filter (NBA, NFL, etc.).
include_scoreNoInclude similarity scores for debugging.
min_similarityNoMinimum similarity score for the semantic match.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds real value by stating the return shape is performer cards rather than events, but it says nothing about pagination/limit behavior or how partial name matches are ranked, even though min_similarity and limit exist. Adequate, with a clear behavioral gap.

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, front-loaded with the primary action and examples, then the disambiguation. No filler, no repetition of the tool name, and the sibling reference sits at the end where it belongs.

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 six parameters, full schema coverage, an output schema and read-only annotations, the description covers the essential purpose, filter options and return-type distinction. The only shortfall is that it does not address the similarity-threshold or limit knobs that materially change results, though the schema documents them.

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 one of the six parameters is already documented in structured form and the baseline of 3 applies. The description confirms the query is a name lookup and that genre/sport are optional filters, but adds no semantics beyond that (e.g., whether genre/sport narrow or re-rank results).

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?

Names a specific verb and resource ('Find a performer (artist, team or comedian) on XP by name'), lists the filter capabilities, and gives concrete examples ('Phish', 'the Lakers') that show the expected query granularity. The final clause explicitly distinguishes the return type from event search, so an agent can tell it apart from search_events 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 Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly routes the agent: use this to resolve a performer entity, then call search_events with the performer's name to get upcoming events. That is a named alternative plus the condition that selects it, which is exactly the when-to-use routing an agent needs between these two siblings.

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