Skip to main content
Glama

Search festivals

search_festivals
Read-onlyIdempotent

Search music festivals by name, country, genre, month or date range. Returns upcoming festivals by default, with dates, location, genres and links (festival page, tickets).

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_festivals"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoLatest date, YYYY-MM-DD.
fromNoEarliest date, YYYY-MM-DD.
genreNoGenre, e.g. "techno", "metal", "country".
limitNoMax results, 1-25. Default 10.
monthNoCalendar month as YYYY-MM, e.g. "2026-11".
queryNoFestival name or part of it. Omit to browse by filters alone.
countryNoCountry name, e.g. "Australia", "United Kingdom", "Scotland".
include_pastNoInclude festivals that have already ended. Default false.

Output Schema

NameRequiredDescriptionDefault
sourceYes
returnedNo
festivalsNo
totalMatchesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • removedOutput schema / properties / festivals / items / properties / endDate / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / festivals / items / properties / endDate / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / festivals / items / properties / startDate / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / festivals / items / properties / startDate / type
      Added value: +[
      +  "string",
      +  "null"
      +]
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive, closed-world behavior, and the description adds the meaningful extra: results are scoped to upcoming festivals unless overridden, and the payload includes dates, location, genres and outbound links. It stops short of noting pagination limits or how multiple filters combine.

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, both front-loaded: the searchable dimensions come first, then the default result behavior and payload. No filler or redundant restatement of the tool name.

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 an output schema present, the description needn't detail return values, and annotations carry the safety profile. For an 8-parameter, all-optional search tool the only real gap is combined-filter semantics (AND vs OR) and whether an empty query returns the full upcoming list.

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 the schema already documents every parameter including date formats and the 1-25 limit range. The description only restates the filter categories at a high level and adds no syntax or interplay detail beyond the schema, 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 ("Search music festivals") and enumerates the five filterable dimensions, plus the default result set (upcoming). An agent can distinguish it from get_festival (single-record lookup) and search_artists without opening the schema.

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?

The phrase "Returns upcoming festivals by default" implicitly tells the agent when to reach for include_past, and "browse by filters alone" lives in the schema rather than the description. There is no explicit statement of when to use this versus get_festival or whats_on, so routing still requires inference.

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