Skip to main content
Glama

calendar

Read-only

Generate month views with ISO week numbers and optional holidays, then resolve date queries such as the last Friday of November 2026 or 2027-W12.

Instructions

Month calendars with ISO weeks and optional holidays; query: "last friday of november 2026", "3rd monday of may 2027", "2027-W12".

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

Input Schema

NameRequiredDescriptionDefault
yearNo
monthNo
queryNo
monthsNocount
regionNo
countryNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.2

TDQS

B3.2/5.0
Behavior3/5

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

readOnlyHint=true already establishes this is a safe read, and the description legitimately adds that output includes ISO week numbers and that holidays are opt-in rather than automatic. Beyond that it stays silent on behaviors that matter for a 6-optional-param tool: what the defaults are when nothing is supplied, how region vs country affect the holiday overlay, and how conflicting query + year/month inputs resolve.

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?

A single front-loaded clause states the core capability, then examples appear immediately where an agent needs them for query construction. The telegraphic 'query:' fragment and the leading semicolon are slightly clipped, but nothing is padded and nothing is wasted.

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?

Given there is no output schema, the description does supply the shape of the result (a month calendar annotated with ISO weeks, optionally with holidays), which is the main thing an agent needs. What it omits — default range when called with no args, and the meaning of region/country — is real but modest for a read-only convenience tool.

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 only 17% (only 'months' carries a terse 'count'), so the description must carry weight, and it does for the hardest parameter: 'query' is explained with three worked examples covering relative phrases, ordinal weekdays, and ISO week notation. However year, month, months, region, and country get no semantic treatment at all — the words 'optional holidays' only hint at region/country, leaving five of six parameters opaque.

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 names the resource (month calendars) and the two defining traits: ISO weeks and optional holidays, plus a natural-language/ISO-week query capability illustrated with three concrete examples. It is clear what the tool produces, though it never contrasts itself with the sibling 'holidays' tool, so an agent cannot tell from the text which one to reach for when it only wants holiday dates.

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

Usage Guidelines2/5

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

The example query strings demonstrate syntax but say nothing about when to use this tool versus 'holidays', 'date_add', or 'date_diff'. There is no guidance on what happens with no arguments, whether query overrides year/month, or when to prefer structured params over a query string.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.