holiplan
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_holiday_windowsA | School holiday windows and public holidays for a region and year. Use this to frame the year before discussing destinations. Each school window has its official dates and its effective dates, stretched
over the weekends and public holidays that touch it -- the days the family
can actually be away. Holidays of two school days or fewer are listed
separately as |
| calculate_leave_costB | Leave days needed to be away from Accounts for weekends, public holidays inside the trip, and any half days, part-time pattern or local-holiday settings in the ledger's profile. |
| find_bridge_daysC | The leave days that buy the most time off, best value first. Each option says which days to take off, the stretch that buys, days off
per leave day, the public holidays that make it a bridge, and |
| get_year_budgetB | Leave planned versus available for a year, including carryover expiry. Answers "can we afford all of this?" -- call it after every change. |
| upsert_tripB | Add or update one trip in the ledger, then re-check the whole ledger. Returns the updated ledger plus any issues. Hand the ledger back to the user so they can save it. |
| check_ledgerA | Validate the whole ledger: overlaps, budget breaches, bad dates, and trips that fall outside the school holidays. Run this before telling the user a plan works. |
| list_deadlinesB | Dated actions the plan implies: booking deadlines and cancel-by dates. Use it to answer "what needs doing next?". |
| summarise_planB | The whole plan at a glance, for a brief to a partner or a quick recap. Returns the family, leave per year, every trip with its leave cost and
booking state, each school window with the plans in it, |
| export_icsB | The ledger as an .ics calendar file the user can import. Returns file contents -- tell the user to save it and import it. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| set_up_profile | Create the family profile and a first ledger, one question at a time. |
| plan_my_year | Walk through planning a whole year of family holidays. |
| plan_window | Pick a destination for one holiday window. |
| whats_next | Deadlines and problems in the plan, most urgent first. |
| partner_brief | A short, plain summary of the plan for the other parent. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| ledger_schema | JSON schema for the ledger file: schema version, profile and trips. |
| profile_schema | JSON schema for the family profile inside the ledger. |
| trip_schema | JSON schema for one trip, including its bookings. |
| starter_ledger_resource | A blank ledger to fill in: placeholder country, no trips, zero leave. |
TDQS
Scored across 9 tools
Most tools have clearly distinct purposes: holiday lookup, leave-cost calculation, bridge-day discovery, budgeting, trip upsert, validation, deadlines, summarisation, and export. Some overlap exists among get_year_budget, check_ledger, and summarise_plan, since all can surface budget or ledger issues, but their primary intents are different enough that an agent should usually choose correctly.
All tool names use snake_case with a consistent verb_noun or verb_object pattern: get_holiday_windows, calculate_leave_cost, find_bridge_days, upsert_trip, check_ledger, list_deadlines, summarise_plan, export_ics. The only minor variation is export_ics being noun-oriented rather than verb_noun, but it still fits the convention and is unambiguous.
Nine tools is well-scoped for a holiday/leave planning server. Each tool covers a distinct part of the workflow, and there is no obvious bloat or missing core capability that would require several extra tools.
The surface covers the main lifecycle: holiday windows, leave cost, bridge days, budget, trip upsert, validation, deadlines, summary, and calendar export. The main gap is the absence of an explicit delete_trip or remove operation, though upsert_trip may allow updates and agents can likely work around this for most planning tasks.