Nexxupp MCP Server

Official

by Nexxupp-Organization

Overview Schema Source Related Servers Discussions Admin

TypeScript

Hybrid

calendar_delete_event

Delete a calendar event by its unique ID to manage your schedule and remove outdated appointments.

Instructions

Delete an event by id.

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": {
      "eventId": "<eventId>"
    },
    "name": "calendar_delete_event"
  }
}

Input Schema

Name	Required	Description	Default
`eventId`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 3, 2026

TDQS

C2.7/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 burden. It does not say whether deletion is permanent or recoverable, how recurring events are handled, whether attendees are notified, or what permissions are required. Only the destructive verb 'delete' hints at the risk profile.

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?

A single short sentence with the action front-loaded and zero filler. It is efficient, though the brevity is partly the result of under-specification rather than disciplined editing.

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

Completeness2/5

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

This is a destructive mutation with no annotations, no output schema, and no documented side effects. An agent has no information about reversibility, error behavior when the id is missing, or required scopes, which is insufficient for a deletion tool.

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

Parameters2/5

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

Schema description coverage is 0% for the single required parameter. The phrase 'by id' only echoes the property name eventId and adds no format, source, or validation detail (e.g., where the id comes from, whether it accepts recurrence ids). The description does not compensate for the coverage gap.

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 (delete) and resource (event) plus the keying mechanism (by id), so an agent immediately knows what the tool does. However, it does nothing to distinguish it from the sibling calendar_update_event or to clarify scope (single event vs. recurring series).

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no prerequisites, and no mention of alternatives such as calendar_update_event. The agent must infer that this is the terminal removal operation from the verb alone.

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