Skip to main content
Glama

lacita

by app.lacita.api

add_calendar_reminder

Add a reminder configuration to a calendar. Supports two types: "relative" (X minutes before) or "specific_time" (specific time on day before). Max 5 reminders per calendar.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
calendarIdYesThe calendar ID
daysBeforeNoFor specific_time reminders: days before appointment (0 = same day, 1 = day before). Max 30.
reminderTypeYesType of reminder: "relative" for X minutes before, "specific_time" for specific time of day
specificTimeNoFor specific_time reminders: time in HH:mm format (e.g., "20:00" for 8 PM)
minutesBeforeNoFor relative reminders: minutes before appointment (e.g., 1440 = 24 hours, 60 = 1 hour). Min 5, max 43200 (30 days).

TDQS

A4.2/5.0
Behavior4/5

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

Annotations indicate a non-read-only, non-destructive operation. The description adds value by disclosing the maximum of 5 reminders per calendar and the two modes (relative/specific_time), which are behavioral constraints not visible in annotations. It does not contradict 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 two sentences, front-loaded with the primary purpose, and every clause contributes meaningful information (types, limit). No wasted words.

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?

The description covers the essential behavior (add reminder, two types, max 5) and the schema documents all parameters. While it doesn't explain success/error responses, that is not required given no output schema, and the operation's scope is simple enough.

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 the baseline is 3. The description reinforces the meaning of the reminder types but does not add new details about conditional dependencies or parameter formats 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 clearly states the action ('Add a reminder configuration to a calendar') with a specific verb and resource. It distinguishes the tool from siblings by specifying the two reminder types and the limit of 5, making it unambiguous.

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?

The description implies usage by explaining the two supported reminder types and the max limit. It does not explicitly name alternatives, but the context is clear and there are no exclusions; the sibling tools naturally indicate when this is the add operation vs. delete/get.

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

All lacita 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.5/5.0
Disambiguation3/5

Most tools are clearly distinct, but update_calendar overlaps with specialized tools like update_booking_settings, update_confirmation_settings, and the reminder management tools (add/delete/get reminders). This creates ambiguity about which tool to use for modifying specific settings such as buffers or reminders, though descriptions help clarify the intended scope.

Naming Consistency5/5

All 28 tools follow a consistent verb_noun snake_case pattern (e.g., create_calendar, get_appointments, update_contact). The verbs are predictable (add, cancel, create, delete, get, reschedule, send, update), making the API easy to navigate.

Tool Count2/5

With 28 tools, the set exceeds the 25+ threshold typically considered too many. While each tool serves a legitimate purpose, the high number is overwhelming and likely includes more granularity than necessary; some settings tools could be consolidated.

Completeness5/5

The tool surface covers the full lifecycle of calendars, appointments, and contacts, including availability, overrides, reminders, confirmation settings, and notifications. There are no obvious dead ends or missing operations; cancellation and rescheduling handle appointment changes, and send_invitation covers creation.

Resources