Skip to main content
Glama

haus

by app.onehaus

create_recurring_calendar_event

Create a recurring calendar event that automatically generates event instances on a schedule.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
notesNoFreeform notes applied to every generated instance. Up to 5000 characters.
titleYesEvent title/summary applied to every generated instance. Required, up to 200 characters.
endDateNoLast date on which instances may occur, YYYY-MM-DD format. Omit for no end date (bounded only by maxOccurrences, if set).
durationNoLength of each instance, in ISO 8601 duration format.
isAllDayNoTrue if generated instances are all-day events with no specific start/end time; false for timed instances.
locationNoLocation applied to every generated instance. Set $type to 'Address' for physical (with line1-3, postalCode, countryCode) or 'OnlineLocation' for virtual (with url, notes).
timezoneNoIANA timezone id (e.g. 'Europe/London') that startTime is in. Each generated occurrence's UTC instant respects this zone's DST.
startDateNoAnchor date the recurrence is calculated from, YYYY-MM-DD format. The first instance falls on this date (subject to startTime/timezone); later instances are startDate plus multiples of the cronExpression interval.
startTimeNoTime of day each instance starts, in HH:mm:ss format (local to timezone). Omit for an event with no fixed time.
descriptionNoLonger free-text description applied to every generated instance. Up to 2000 characters.
cronExpressionYesRecurrence interval, NOT a cron expression despite the field name. Format is 'N Unit' where N is a positive integer and Unit is one of Day, Week, Month, Year (case-sensitive), e.g. '1 Day', '2 Week', '1 Month', '1 Year'. Instances recur every N of the given unit starting from startDate.
maxOccurrencesNoMaximum number of instances to generate before recurrence stops. Omit for unlimited (bounded only by endDate, if set).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
itemsYes
titleNo
messageNo
variantNo

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed32 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "cronExpression": "1 Week",
+    "description": "Sync on sprint progress",
+    "duration": "PT30M",
+    "endDate": "2026-12-31",
+    "isAllDay": false,
+    "maxOccurrences": 20,
+    "notes": "Bring your laptop",
+    "startDate": "2026-08-03",
+    "startTime": "09:00:00",
+    "timezone": "Europe/London",
+    "title": "Weekly team standup"
+  }
+]
    • changedInput schema / properties / cronExpression / description
      Previous value: -"Cron expression for recurrence. Format: minute hour dayOfMonth month dayOfWeek"New value: +"Recurrence interval, NOT a cron expression despite the field name. Format is 'N Unit' where N is a positive integer and Unit is one of Day, Week, Month, Year (case-sensitive), e.g. '1 Day', '2 Week', '1 Month', '1 Year'. Instances recur every N of the given unit starting from startDate."
    • addedInput schema / properties / cronExpression / examples
      Added value: +[
+  "1 Week"
+]
    • addedInput schema / properties / description / description
      Added value: +"Longer free-text description applied to every generated instance. Up to 2000 characters."
    • changedInput schema / properties / duration / description
      Previous value: -"Duration in ISO 8601 format, e.g. PT1H30M"New value: +"Length of each instance, in ISO 8601 duration format."
    • addedInput schema / properties / duration / examples
      Added value: +[
+  "PT30M"
+]
    • changedInput schema / properties / endDate / description
      Previous value: -"YYYY-MM-DD format"New value: +"Last date on which instances may occur, YYYY-MM-DD format. Omit for no end date (bounded only by maxOccurrences, if set)."
    • addedInput schema / properties / endDate / examples
      Added value: +[
+  "2026-12-31"
+]
    • addedInput schema / properties / isAllDay / description
      Added value: +"True if generated instances are all-day events with no specific start/end time; false for timed instances."
    • addedInput schema / properties / isAllDay / examples
      Added value: +[
+  false
+]
    • changedInput schema / properties / location / description
      Previous value: -"Location. Set $type to 'Address' for physical (with line1-3, postalCode, countryCode) or 'OnlineLocation' for virtual (with url, notes)."New value: +"Location applied to every generated instance. Set $type to 'Address' for physical (with line1-3, postalCode, countryCode) or 'OnlineLocation' for virtual (with url, notes)."
    • addedInput schema / properties / location / properties / countryCode / description
      Added value: +"Country code for the address (Address type)."
    • addedInput schema / properties / location / properties / countryCode / examples
      Added value: +[
+  "GB"
+]
    • addedInput schema / properties / location / properties / line1 / description
      Added value: +"First line of the street address (Address type). At least one of line1-3/postalCode is required when $type is 'Address'."
    • addedInput schema / properties / location / properties / line1 / examples
      Added value: +[
+  "221B Baker Street"
+]
    • addedInput schema / properties / location / properties / line2 / description
      Added value: +"Second line of the street address (Address type), e.g. building or suite."
    • addedInput schema / properties / location / properties / line3 / description
      Added value: +"Third line of the street address (Address type)."
    • addedInput schema / properties / location / properties / notes / description
      Added value: +"Notes about the location, e.g. parking instructions or a meeting passcode. Up to 500 characters for OnlineLocation."
    • addedInput schema / properties / location / properties / postalCode / description
      Added value: +"Postal or ZIP code (Address type). Up to 20 characters."
    • addedInput schema / properties / location / properties / postalCode / examples
      Added value: +[
+  "NW1 6XE"
+]
    • changedInput schema / properties / location / properties / url / description
      Previous value: -"URL for online locations"New value: +"URL for online locations (OnlineLocation type). Must be an absolute http/https URL."
    • addedInput schema / properties / location / properties / url / examples
      Added value: +[
+  "https://meet.google.com/abc-defg-hij"
+]
    • addedInput schema / properties / maxOccurrences / description
      Added value: +"Maximum number of instances to generate before recurrence stops. Omit for unlimited (bounded only by endDate, if set)."
    • addedInput schema / properties / maxOccurrences / examples
      Added value: +[
+  20
+]
    • addedInput schema / properties / notes / description
      Added value: +"Freeform notes applied to every generated instance. Up to 5000 characters."
    • changedInput schema / properties / startDate / description
      Previous value: -"YYYY-MM-DD format"New value: +"Anchor date the recurrence is calculated from, YYYY-MM-DD format. The first instance falls on this date (subject to startTime/timezone); later instances are startDate plus multiples of the cronExpression interval."
    • addedInput schema / properties / startDate / examples
      Added value: +[
+  "2026-08-03"
+]
    • changedInput schema / properties / startTime / description
      Previous value: -"Time of day in HH:mm:ss format"New value: +"Time of day each instance starts, in HH:mm:ss format (local to timezone). Omit for an event with no fixed time."
    • addedInput schema / properties / startTime / examples
      Added value: +[
+  "09:00:00"
+]
    • addedInput schema / properties / timezone / examples
      Added value: +[
+  "Europe/London"
+]
    • addedInput schema / properties / title / description
      Added value: +"Event title/summary applied to every generated instance. Required, up to 200 characters."
    • addedInput schema / properties / title / examples
      Added value: +[
+  "Weekly team standup"
+]
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations only indicate readOnlyHint=false and destructiveHint=false, which align with a create operation. The description adds meaningful behavioral context beyond annotations by stating that the tool 'automatically generates event instances on a schedule', disclosing the recurring side-effect. No contradictions with annotations.

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?

The description is a single, tightly scoped sentence that front-loads the core action ('Create a recurring calendar event'). Every word earns its place, with no fluff or redundancy.

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?

Despite the high complexity (12 params, nested objects, output schema), the description covers the essential behavior for the agent to understand what the tool does. The schema and annotations fill in the remaining details. The only gap is the absence of explicit usage guidelines, but that is covered separately.

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 coverage is 100%, so parameter details are fully documented in the input schema. The description itself does not add parameter-specific meaning, which is acceptable per the baseline for high schema coverage. The description contributes nothing beyond what the schema already provides.

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?

The description uses a specific verb-resource pairing ('Create a recurring calendar event') and clearly distinguishes this from the sibling create_calendar_event by adding 'recurring' and 'automatically generates event instances on a schedule.' This leaves no ambiguity about the tool's function.

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?

The description implies usage for recurring events but does not explicitly state when to use this tool over create_calendar_event or other alternatives. It mentions 'recurring' and 'schedule', which implies a distinction, but there is no direct 'when to use / when not to use' guidance or reference to sibling tools.

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

All haus toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.9/5.0
Disambiguation5/5

Each tool targets a distinct resource and action, with clear descriptions separating similar-sounding tools like create_calendar_event vs create_recurring_calendar_event. Shopping list operations (add, buy, remove, update) are clearly delineated.

Naming Consistency5/5

All tools follow a verb_noun snake_case pattern: create_*, list_*, update_*, delete_*, get_*, etc. Even special operations like store_memory, recall_memory, and skip_recommendation fit the pattern.

Tool Count1/5

With 68 tools, this server vastly exceeds a reasonable scope; the instruction manual indicates 50+ tools is an extreme mismatch. The breadth suggests the server should be split into focused sub-servers (tasks, shopping, calendar, etc.) rather than a single monolithic interface.

Completeness5/5

The tool surface covers full CRUD/lifecycle for all major resources: tasks, shopping, calendar, contacts, documents, appliances, vehicles, pets, recipes, meal plans, subscriptions, and memories. Additional features like house review, weather, and profile round out the household management domain.

Resources