lacita

send_invitation

Send an appointment invitation to a client on behalf of the service provider. The visitor will receive a confirmation request. Check availability first using get_calendar_availability. You can reference an existing contact by contactId, or provide firstName/email/phone directly.

Input Schema

TableJSON Schema

Name	Required	Description
`email`	No	Email of the client
`notes`	No	Optional notes
`phone`	No	Phone of the client
`endTime`	Yes	End time in ISO 8601 format (e.g., 2025-01-15T10:45:00Z)
`lastName`	No	Last name of the client
`location`	No	Optional meeting location
`contactId`	No	Existing contact ID (optional — if provided, firstName/email/phone are used from the contact)
`firstName`	Yes	First name of the client
`startTime`	Yes	Start time in ISO 8601 format (e.g., 2025-01-15T10:00:00Z)
`calendarId`	Yes	The calendar ID

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already indicate a write operation (readOnly=false) and non-idempotent, non-destructive properties. The description adds valuable side-effect information by stating the visitor will receive a confirmation request and that the invitation is sent on behalf of the provider, going beyond the structured 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 three sentences with no filler. It front-loads the main action, then adds the side effect and usage prerequisite, earning every word.

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 10-parameter write tool with no output schema, the description provides essential context: purpose, side effect, prerequisite (availability check), and contact identification modes. It does not explain return values or error cases, but this is minimally sufficient given the schema and annotations.

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% with all parameters described. The description reiterates the contactId vs direct-fields relationship, which is already in the schema, and adds no new parameter-specific details. Therefore, it stays at the baseline for a fully documented schema.

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 a specific action: sending an appointment invitation to a client on behalf of the service provider. This distinguishes it from sibling tools like cancel_appointment and reschedule_appointment by naming the unique operation and the recipient.

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

Usage Guidelines5/5

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

It explicitly instructs to check availability first using get_calendar_availability, providing a clear precondition. It also explains the two contact-identification modes (contactId vs direct fields), giving practical usage context for when to use this tool.

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

All lacita tools Inspect

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

Need Help?