Skip to main content
Glama

School holidays

get_school_holidays
Read-onlyIdempotent

School holiday dates in the UK for a calendar year (half terms, Easter, summer, Christmas, and training days). With council, that council's published term dates, each school year with the council's source link and the date Leave Hacker last checked it; for a school year it hasn't published, and without a council, TYPICAL dates, which are the usual pattern and not official (Northern Ireland: the Department of Education's dates). Every holiday says which it is. Academies and independent schools can set their own, so tell the person to check their school's.

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

Input Schema

NameRequiredDescriptionDefault
yearNoCalendar year, e.g. 2027. Defaults to this year.
regionNoUK nation: england-and-wales, scotland or northern-ireland. Defaults to england-and-wales, or to the council's nation when council is given.
councilNoThe UK council whose term dates the school follows: its name ("Surrey", "Edinburgh"), its id ("surrey", "city-of-edinburgh") or the first half of a postcode ("GU1", "EH1"), looked up in Leave Hacker's own copy of the ONS list. Send only the first half of a postcode, not the full one.

Output Schema

NameRequiredDescriptionDefault
yearYes
notesYes
caveatYes
regionYes
councilYesThe council whose published dates are used, or null for typical dates
typicalYesTrue when every date here is typical, not published
regionNameYes
schoolYearsYesWhere each school year's dates come from
trainingDaysYesThe council's staff training (INSET) days: pupils are off, staff work
schoolHolidaysYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed12 schema fields changed
    • addedInput schema / properties / council
      Added value: +{
      +  "description": "The UK council whose term dates the school follows: its name (\"Surrey\", \"Edinburgh\"), its id (\"surrey\", \"city-of-edinburgh\") or the first half of a postcode (\"GU1\", \"EH1\"), looked up in Leave Hacker's own copy of the ONS list. Send only the first half of a postcode, not the full one.",
      +  "maxLength": 80,
      +  "minLength": 2,
      +  "type": "string"
      +}
    • removedInput schema / properties / region / default
      Removed value: -"england-and-wales"
    • changedInput schema / properties / region / description
      Previous value: -"UK nation: england-and-wales, scotland or northern-ireland."New value: +"UK nation: england-and-wales, scotland or northern-ireland. Defaults to england-and-wales, or to the council's nation when council is given."
    • addedOutput schema / properties / council
      Added value: +{
      +  "anyOf": [
      +    {
      +      "additionalProperties": false,
      +      "properties": {
      +        "id": {
      +          "type": "string"
      +        },
      +        "name": {
      +          "type": "string"
      +        },
      +        "nation": {
      +          "type": "string"
      +        },
      +        "short": {
      +          "type": "string"
      +        }
      +      },
      +      "required": [
      +        "id",
      +        "name",
      +        "short",
      +        "nation"
      +      ],
      +      "type": "object"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "description": "The council whose published dates are used, or null for typical dates"
      +}
    • addedOutput schema / properties / notes
      Added value: +{
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
    • addedOutput schema / properties / schoolHolidays / items / properties / typical
      Added value: +{
      +  "type": "boolean"
      +}
    • changedOutput schema / properties / schoolHolidays / items / required
      Previous value: -[
      -  "name",
      -  "start",
      -  "end",
      -  "days"
      -]New value: +[
      +  "name",
      +  "start",
      +  "end",
      +  "days",
      +  "typical"
      +]
    • addedOutput schema / properties / schoolYears
      Added value: +{
      +  "description": "Where each school year's dates come from",
      +  "items": {
      +    "additionalProperties": false,
      +    "properties": {
      +      "checked": {
      +        "description": "yyyy-MM-dd the dates were last checked against it",
      +        "type": "string"
      +      },
      +      "council": {
      +        "type": "string"
      +      },
      +      "note": {
      +        "type": "string"
      +      },
      +      "schoolYear": {
      +        "description": "e.g. \"2026/27\"",
      +        "type": "string"
      +      },
      +      "source": {
      +        "description": "council: the council's published term dates; typical: the usual pattern, not official",
      +        "enum": [
      +          "council",
      +          "typical"
      +        ],
      +        "type": "string"
      +      },
      +      "sourceUrl": {
      +        "description": "The council's own page or PDF",
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "schoolYear",
      +      "source"
      +    ],
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
    • addedOutput schema / properties / trainingDays
      Added value: +{
      +  "description": "The council's staff training (INSET) days: pupils are off, staff work",
      +  "items": {
      +    "additionalProperties": false,
      +    "properties": {
      +      "date": {
      +        "description": "yyyy-MM-dd",
      +        "type": "string"
      +      },
      +      "label": {
      +        "description": "e.g. \"Fri 26 Mar 2027\"",
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "date",
      +      "label"
      +    ],
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
    • removedOutput schema / properties / typical / const
      Removed value: -true
    • addedOutput schema / properties / typical / description
      Added value: +"True when every date here is typical, not published"
    • changedOutput schema / required
      Previous value: -[
      -  "region",
      -  "regionName",
      -  "year",
      -  "typical",
      -  "schoolHolidays",
      -  "caveat"
      -]New value: +[
      +  "region",
      +  "regionName",
      +  "year",
      +  "typical",
      +  "council",
      +  "schoolYears",
      +  "trainingDays",
      +  "schoolHolidays",
      +  "notes",
      +  "caveat"
      +]
  2. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnly/openWorld/idempotent/non-destructive, so the bar is lower, yet the description still adds meaningful context: data provenance (Leave Hacker's own copy of the ONS list), per-year source links and a last-checked date, and that TYPICAL dates are unofficial while Northern Ireland uses the Department of Education's dates. It also flags a user-facing caveat about academies and independent schools.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is front-loaded, but the body is a dense run-on of semicolon-separated clauses mixes data description with fallback logic and caveats, making it harder to parse than it needs to be. Content largely earns its place, though the ordering could be cleaner.

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

Completeness3/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 needn't be detailed, and the description does cover the complicated council/no-council fallback thoroughly. It is nearly complete for a 3-parameter read tool, with the only real gap being guidance on sibling alternatives.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so a 3 is the baseline, but the description genuinely adds semantics: council lookup accepts name, id, or postcode first half, and region defaults to the council's nation. The published-vs-typical fallback logic clarifies what result a given parameter combination produces.

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 verb and resource ('School holiday dates in the UK for a calendar year') and enumerates the covered holiday types (half terms, Easter, summer, Christmas, training days). It does not explicitly name a sibling to distinguish itself from, e.g. get_bank_holidays, 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?

It gives useful conditional guidance on operating modes: with a council, results are that council's published term dates; without one, they are TYPICAL dates. However it never says when to prefer this tool over nearby siblings such as get_bank_holidays or plan_leave_year, so usage is implied rather than stated.

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