Skip to main content
Glama
langmail-mcp

langmail-mcp

Official
by langmail

Respond to calendar event

respond_to_event

Respond to calendar invitations by accepting, declining, or setting tentative status for the authenticated user; updates their attendee status without changing the event.

Instructions

RSVP to a calendar invite or meeting invitation on the authenticated user’s behalf — accept, decline, or answer tentative/maybe. Sets their own attendee status on the event (identified by its uid from list_calendar_events) and saves it back. The organizer is notified automatically. Use this to reply to an invitation you received; it does not change the event itself. Defaults to the user’s default calendar; pass calendarUrl if the event lives in another calendar.

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": {
      "response": "<response>",
      "uid": "<uid>"
    },
    "name": "respond_to_event"
  }
}

Input Schema

NameRequiredDescriptionDefault
uidYes
responseYes
calendarUrlNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations only declare the generic profile (not read-only, not idempotent, not destructive, open-world); the description adds genuinely new behavior — it mutates only the caller's own attendee status, the organizer is notified automatically, and results are saved back. No permissions or auth prerequisites are described, which is the main remaining gap.

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?

Front-loaded with the action and three compact sentences, each carrying distinct information (what it does, side effects, parameter defaults). Minor redundancy in 'calendar invite or meeting invitation', but no filler.

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?

With no output schema and no parameter descriptions, the description supplies what an agent needs to call it correctly — parameter origins, defaults, and the notification side effect. It omits error/edge behavior (e.g., what happens if the user isn't an attendee), which would round it out.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must carry the load and it does: it explains the semantics of response (accept/decline/tentative-maybe), the origin of uid (from list_calendar_events), and the default behavior of calendarUrl (defaults to the user's default calendar).

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?

States a specific verb (RSVP) and resource (calendar invite) plus the exact response options, and explicitly says what it does not do ('does not change the event itself') — separating it from update_calendar_event and create_calendar_event.

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?

Clearly scopes use to replying to an invitation you received, points to list_calendar_events as the source of the uid, and explains when to pass calendarUrl. It excludes event modification but never names the sibling to use instead for that purpose, so it stops short of a full when-to-use/when-not matrix.

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