Skip to main content
Glama

Generate printable calendar

generate_calendar
Read-onlyIdempotent

Use this when the user wants a printable calendar ("printable calendar", "2027 calendar printable", "monthly calendar template", "yearly calendar", "wall calendar", "school year calendar", "calendar with holidays") as a PDF. Builds a year on one page, a 12-month wall calendar with cover, a single month, or a month range up to 24 months, with public holidays for a country and state, custom birthdays and events, Monday or Sunday weeks, ISO week numbers, notes lines, paper size, language and an accent colour. Returns a preview and a PDF download link. Does not add events to Google, Outlook or Apple calendars, does not schedule meetings, and does not draw lunar, Hijri or Hebrew calendars.

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": {
      "layout": "<layout>"
    },
    "name": "generate_calendar"
  }
}

Input Schema

NameRequiredDescriptionDefault
endNoFor layout range: last month as YYYY-MM (at most 24 months after start), e.g. 2027-06.
yearNoYear for layout year or wall, e.g. 2027. Default: next year from October on, otherwise this year.
bleedNoAdd a 0.125 in print bleed with trim marks in the PDF boxes, for professional printing. Default false.
monthNoFor layout month: the month as YYYY-MM, e.g. 2027-03.
notesNoAdd a ruled notes area under each month page (not on the one-page year). Default false.
paperNoPaper size: letter (8.5x11 in), a4, a3 or tabloid (11x17 in). Default letter for US/Canada/Mexico, a4 for other countries.
startNoFor layout range: first month as YYYY-MM, e.g. 2026-08.
titleNoOptional title printed on the calendar, e.g. "Kowalski Family 2027". Default: the year or month.
accentNoOne accent colour for headings and holiday marks: a hex code like #0F766E or a name (indigo, blue, navy, teal, green, olive, red, crimson, pink, purple, orange, amber, brown, slate, gray, black). Default indigo.
eventsNoCustom events and birthdays (up to 60). Example: [{"date":"03-04","title":"Mom's birthday"},{"date":"2027-06-12","title":"Wedding"}]
layoutYesyear = whole year on one page; wall = 12-month wall calendar, a cover plus one month per page; month = one month on one page; range = one page per month from start to end (e.g. a school year). Example: wall
countryNoCountry for public holidays: ISO two-letter code or name, e.g. US, GB, DE, PL, FR, JP, BR, AU, CA. Omit for a calendar without holidays.
holidaysNoShow public holidays when a country is given. Default true; false hides them.
languageNoLanguage for month and weekday names: en (default), pl, de, es, fr, it, pt, nl or ja. Holiday names use this language when the country's data has it, else English. Example: de
week_startNoFirst day of each week row. Default: the country's custom (Sunday for US, CA, BR, JP...; Monday for most of Europe); without a country, Sunday for English, Monday otherwise. Example: monday
orientationNoPage orientation. Default landscape. Example: portrait
start_monthNoFirst month (1-12) for a 12-month year or wall calendar; 8 makes an August-to-July academic calendar. Default 1.
subdivisionNoOptional state, province or region for local holidays, e.g. TX or CA (US), BY (Bavaria, DE), SCT (Scotland), NSW (AU), ON (CA).
week_numbersNoPrint ISO 8601 week numbers beside each week row. Default false. Example: true
include_observancesNoAlso show observances, bank and optional days (e.g. Mother's Day, Valentine's Day, Christmas Eve). Default false: public holidays only.

Output Schema

NameRequiredDescriptionDefault
kindYes
namesYes
notesYes
pagesYes
paperYes
titleYes
accentYes
eventsYes
inputsYes
layoutYes
monthsYes
periodYes
regionYes
holidaysYes
languageYes
downloadsYes
notes_areaYes
page_countYes
week_startYes
event_countYes
orientationYes
week_numbersYes
holiday_countYes
holidays_shownYes
include_observancesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description only needs to add operational context — and it does, stating that it returns a preview plus a PDF download link. It also bounds the range layout at 24 months and scopes holiday data to a country/state, but says nothing about generation time, file retention, or failure modes.

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 sentences, front-loaded with the selection triggers and followed by the capability rollup — no filler. The middle feature enumeration is dense but each item maps to a real parameter, so little could be cut without losing routing or configuration signal.

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?

For a 20-parameter tool, the description plus a 100%-covered schema, an output schema, and full annotations leave nothing critical unstated: output form (preview + PDF link), scope limits, and exclusions are all covered. Remaining gaps (e.g. behavior when country is omitted, error cases) are already handled by the schema, so the description is adequate but not exhaustive.

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 description coverage is 100%, so the baseline is 3; the description earns an extra point by rolling the 20 parameters into a readable capability summary (layouts, holidays by country/state, custom birthdays/events, week start, ISO week numbers, notes, paper size, language, accent colour) that tells an agent what is configurable before opening the schema. It adds framing rather than new syntax or format detail, so it stays below 5.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names a specific verb+resource (generate a printable calendar as a PDF) and enumerates the concrete layouts produced: one-page year, 12-month wall calendar with cover, single month, and range. It is unmistakably distinct from event-creation tools because it explicitly states it does not add events to Google/Outlook/Apple calendars.

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?

Opens with an explicit 'use this when the user wants…' trigger and lists the exact phrasings that select it ("printable calendar", "wall calendar", "school year calendar"), which is strong routing guidance. It also lists when-not conditions (no event scheduling, no lunar/Hijri/Hebrew calendars), though it never names the sibling find_holidays or explains how they relate.

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