Skip to main content
Glama

Halloween, Christmas and other seasonal events

seasonal_events
Read-onlyIdempotent

List upcoming dated seasonal events in Manchester, such as Halloween parties and club nights, or Christmas markets, light trails, panto and concerts. Use for questions like "Halloween in Manchester", "Christmas markets dates" or "festive things to do in Manchester". Each result has dates, times, prices and a ticket link.

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

Input Schema

NameRequiredDescriptionDefault
seasonNoOptional: halloween, bonfire, christmas or new-years-eve (words like spooky, fireworks, festive or nye work too). Leave out to get every upcoming seasonal event.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / season / description
      Previous value: -"Optional: halloween, bonfire, christmas or new-years-eve. Leave out to get every upcoming seasonal event."New value: +"Optional: halloween, bonfire, christmas or new-years-eve (words like spooky, fireworks, festive or nye work too). Leave out to get every upcoming seasonal event."
  2. Changed1 schema field changed
    • changedInput schema / properties / season / description
      Previous value: -"Optional: halloween, bonfire or christmas. Leave out to get every upcoming seasonal event."New value: +"Optional: halloween, bonfire, christmas or new-years-eve. Leave out to get every upcoming seasonal event."
  3. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare the safe read-only, idempotent, non-destructive profile, so the description's added value is its disclosure of scope ('upcoming dated events', Manchester-only) and the result contents (dates, times, prices, ticket link). With no output schema, noting what comes back is genuinely useful context. It stops short of mentioning pagination or result counts, but only counts as a minor 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?

Three tight sentences: the capability is front-loaded, the example queries sit in the middle, and the return contents close it out. Every sentence earns its place with no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-optional-param read tool with no output schema, the description covers purpose, invocation examples, scoping, and return contents. An agent has everything needed to call it correctly and to know what the results look like.

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%, and the single optional 'season' parameter is fully documented in the schema, including accepted synonyms. The description adds nothing about parameter behavior, so the baseline of 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?

States a specific verb ('List') and resource (upcoming dated seasonal events in Manchester) with concrete instances such as Halloween parties, Christmas markets and panto. The scope is narrower than generic siblings like search_listings or whats_on, though no sibling is named to make the distinction explicit.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

Gives clear usage contexts with sample user questions ('Halloween in Manchester', 'Christmas markets dates', 'festive things to do in Manchester'), which tells the agent when this tool is the right pick. It does not state when NOT to use it or route to a named alternative.

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