MCP Aruba Email & Calendar Server

Overview Schema Source Related Servers Discussions Admin

decline_calendar_event

Declines a calendar event invitation by event UID, with an optional comment explaining the response. Use it to manage schedule availability and notify organizers.

Instructions

Decline a calendar event invitation.

Args: event_uid: UID of the event to decline comment: Optional comment for the decline

Returns: Response status

Example: decline_calendar_event( event_uid="abc123@aruba.it", comment="Purtroppo non posso 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": "decline_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

A3.6/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 behavioral burden for a mutation operation. It says the return is a response status but does not disclose side effects such as notifying the organizer, permission requirements, reversibility, or error behavior.

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 is front-loaded in the first sentence, and the Args and Returns sections are easy to scan. The example is useful but adds some length to an otherwise simple definition.

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?

For a simple two-parameter mutation, the parameters are documented and an output schema exists. However, with no annotations the description should do more to explain side effects and routing versus accept_calendar_event and tentative_calendar_event.

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?

Schema description coverage is 0%, so the description must compensate. It documents both parameters: event_uid as the event UID and comment as optional for the decline, and the example clarifies the UID format.

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 states a specific verb and resource: "Decline a calendar event invitation." The verb "decline" makes it separable from the accept_calendar_event and tentative_calendar_event siblings even though they are not named.

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 by "decline a calendar event invitation," but the description does not explicitly say when to use this instead of accept_calendar_event or tentative_calendar_event. No exclusions or prerequisites are given.

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