Skip to main content
Glama

Calendar: Rsvp event

calendar_rsvp_event
Destructive

Accept, tentatively accept or decline an invitation for the connected account only. Resolve the event first; Outlook organizers cannot RSVP and declining can remove the event from their 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": {
      "calendar_id": "<calendar_id>",
      "event_id": "<event_id>",
      "status": "<status>"
    },
    "name": "calendar_rsvp_event"
  }
}

Input Schema

NameRequiredDescriptionDefault
statusYes
commentNo
event_idYesExact event ID returned by calendar_list_events or calendar_create_event, paired with its parent calendar_id. Calendar event ID: Exact event id in the selected calendar/account. Obtain with: calendar_list_events -> event.id; calendar_create_event -> created event.id Never pass: event title, date.
account_idNoOptional Nilyo connection ID (unipile_account_id from list_connected_accounts). Omit when the user has one account for this provider. When several exist, Nilyo never guesses: list them (display name, identifier, provider user ID), choose the one the user named or ask, and pass its ID here.
calendar_idYesExact calendar ID returned by calendar_list_calendars; never pass a calendar name. Calendar ID: Exact Google/Microsoft calendar id. Obtain with: calendar_list -> calendar.id Never pass: calendar display name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

The description reinforces the destructive nature of the action by stating that declining can remove the event, which is useful context beyond the `destructiveHint: true` annotation. The scope limitation to 'connected account only' is also helpful for behavioral context.

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?

The definition is two sentences long and highly dense with information. It front-loads the primary function and follows with essential constraints and risks, making it efficient and readable.

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 mutation tool tied to complex external calendar logic, the description covers the main constraints (must be resolved) and side effects (event removal). This provides a strong operational picture for an agent.

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

Parameters4/5

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

Given the 60% schema coverage, the description adds crucial semantic value. It provides natural language translations for the `status` enum (e.g., 'maybe' is a 'tentative accept') and gives execution advice for `event_id` ('Resolve the event first').

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 clearly states the tool's function using specific verbs (Accept, tentatively accept, decline) and defines the resource (calendar invitation). While clear, it does not name a sibling tool explicitly to distinguish it from general calendar updates.

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?

It provides critical usage warnings: the operation must be performed on the connected account, and the event must be resolved first. Furthermore, it details the functional consequence of using this tool (declining can remove the event).

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.