Skip to main content
Glama

What's on

whats_on
Read-onlyIdempotent

Festivals happening in a window: this weekend by default, or a calendar month. Filter by country or genre.

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

Input Schema

NameRequiredDescriptionDefault
whenNo"this-weekend" (default) or a month as YYYY-MM.
genreNoGenre.
limitNoMax results, 1-25. Default 10.
countryNoCountry name.

Output Schema

NameRequiredDescriptionDefault
sourceYes
windowYes
festivalsYes
totalMatchesYes

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

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 the safety profile is covered. The description adds only the default time window; it says nothing about what happens with an invalid month format or how results are ordered. That is acceptable given the annotations, but not rich.

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?

One tight sentence with the resource front-loaded, then the default behavior, then the filters. Every clause carries information and nothing is redundant.

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, return values need not be described, and the simple four-optional-parameter shape is well covered by the schema plus the default-window statement. The only meaningful gap is sibling differentiation against search_festivals, which keeps it from a 5.

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%, so all four parameters plus their formats (YYYY-MM, 1-25 limit, default 10) are already documented in the schema. The description restates the default window and the country/genre filters but adds no syntax or edge-case meaning beyond the structured data, so 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 states a specific resource (festivals) and a time scope (this weekend by default, or a calendar month) with filters for country and genre. It is clear on its own, but it never distinguishes itself from sibling tools like search_festivals or get_festival, leaving an agent to guess which one to call.

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 default window ('this weekend by default') and the alternative ('or a calendar month') give implied usage guidance for the `when` parameter. However, there is no explicit when-to-use-this-vs-search_festivals guidance and no exclusions, so routing still depends on 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