MCP Aruba Email & Calendar Server

Overview Schema Source Related Servers Discussions Admin

tentative_calendar_event

Marks a calendar event as tentative (maybe attending) and optionally adds a comment to indicate uncertain participation.

Instructions

Mark a calendar event as tentative (maybe attending).

Args: event_uid: UID of the event comment: Optional comment

Returns: Response status

Example: tentative_calendar_event( event_uid="abc123@aruba.it", comment="Forse riesco a partecipare" )

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": {
      "event_uid": "<event_uid>"
    },
    "name": "tentative_calendar_event"
  }
}

Input Schema

Name	Required	Description	Default
`comment`	No
`event_uid`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.1Nov 9, 2026

TDQS

B3.2/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full disclosure burden. It does not say whether the organizer is notified, whether the change is reversible, what permissions are required, or how recurring events are handled — all material for a mutation tool. 'Returns: Response status' is the only behavioral detail offered.

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 purpose sentence is front-loaded and the Args/Example blocks earn their place by supplying the parameter detail the schema lacks. The Returns line is near-empty filler and the Args list duplicates schema titles, but overall it is compact and well ordered.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need not be explained. For a simple two-parameter tool this is mostly adequate, but the absence of annotations means side effects (notifications, reversibility) remain undocumented.

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 description coverage is 0%, so the description must compensate. It does partially: event_uid is identified as a UID (not a generic ID) and the example shows the expected format ('abc123@aruba.it'), and comment is marked optional. That is useful but stops short of stating whether comment is sent to the organizer.

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?

States a specific verb and resource — 'Mark a calendar event as tentative' — with a clarifying gloss ('maybe attending'). This is clearly distinguishable from the accept/decline/delete siblings, though the description never names them explicitly.

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?

Usage is implied rather than stated: an agent can infer this is the RSVP action for 'maybe' versus accept_calendar_event or decline_calendar_event, but no explicit when-to-use or when-not-to-use guidance is given. No prerequisites (e.g., being an invitee) are mentioned.

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