Skip to main content
Glama

Get festival details

get_festival
Read-onlyIdempotent

Details for one festival: dates, location, venue, genres, description, ticket availability and links. Accepts a festival name, Setline id, or URL slug.

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": {
      "festival": "<festival>"
    },
    "name": "get_festival"
  }
}

Input Schema

NameRequiredDescriptionDefault
festivalYesFestival name, Setline id, or URL slug (e.g. "rock-am-ring-2026").

Output Schema

NameRequiredDescriptionDefault
appNo
hintNo
errorNo
queryNo
sourceYes
festivalNo
didYouMeanNo

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered and the description doesn't need to repeat it. The description adds only the payload inventory, and says nothing about behavior for ambiguous names, missing festivals, or whether the call errors versus returns empty.

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 tight sentences with zero filler, and the resource identity is front-loaded ahead of the accepted input formats. Minor redundancy: the return-field list partially duplicates what the output schema already supplies.

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?

A one-parameter, read-only lookup with an output schema and full annotation coverage is nearly self-describing, and the description covers identity and scope adequately. The remaining gap is resolution behavior when a bare name matches multiple festivals, which an agent would want to know.

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 the single parameter's schema entry already documents 'Festival name, Setline id, or URL slug' with an example. The description restates the same accepted formats nearly verbatim, adding no new meaning such as case-sensitivity or how name collisions are resolved.

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?

"Details for one festival" names a specific verb and resource, and the enumerated payload (dates, location, venue, genres, ticket availability, links) makes the scope concrete. It does not explicitly separate itself from siblings like get_lineup or search_festivals, so it stops 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 only implied: the agent can infer this is the detail-fetch after a search_festivals lookup, but the description never says when to prefer it over get_lineup, get_set_times, or whats_on, nor does it give exclusions. No explicit 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