Prubex

Delete or cancel an event

calendar_delete_event

Destructive

Deletes an event; an occurrence's event_id deletes that occurrence. To delete the whole series, pass the occurrence's series_id as event_id. If this account organises it and others are invited, they get a cancellation. It can return pending_approval: tell the user a person must approve it in Prubex, and do not retry. Use it only when the user asks to cancel or remove the event; to decline someone else's meeting use calendar_respond_to_event. Example: { "event_id": "evt_…" }.

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_id": "<event_id>"
    },
    "name": "calendar_delete_event"
  }
}

Input Schema

Name	Required	Description
`event_id`	Yes	An event id (`evt_…`) from calendar_list_events, or an occurrence’s `series_id` to act on the whole series.
`time_zone`	No	IANA time zone for dates in and out, e.g. "Africa/Johannesburg". Defaults to the workspace time zone, which prubex_overview returns as `time_zone`.
`idempotency_key`	No	Any unique string. Retrying with the same key within 24 h never repeats the action.

Output Schema

Name	Required	Description
`event`	No
`status`	Yes
`message`	Yes	What happened, in words for the user.
`warnings`	No	Accounts that failed or timed out; results from the others are still here.
`account_id`	Yes
`expires_at`	No	When held: when the request expires.
`review_url`	No	When held: where a person approves it in Prubex.
`approval_id`	No	When held: pass it to approvals_get later.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 2, 2026

TDQS

A4.9/5.0

Behavior5/5

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

The annotations already declare destructiveHint=true, readOnlyHint=false, idempotentHint=false and openWorldHint=true, but the description adds important behavioral context beyond them: invited attendees receive a cancellation, the tool may return pending_approval, the user must be told a person must approve it in Prubex, and the agent should not retry. It also explains the occurrence-vs-series deletion semantics.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the core delete behavior, then covers series deletion, cancellation side effects, the pending_approval outcome, and the sibling alternative. Every sentence adds distinct operational value, and the example is compact.

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

Completeness5/5

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

For a destructive calendar mutation with full schema coverage, annotations, and an output schema, the description supplies the remaining agent-critical context: series vs occurrence behavior, attendee cancellation, pending approval handling, and the sibling alternative for declines. Nothing essential for correct invocation is missing.

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 100%, so the schema already documents all three parameters, including the series_id-as-event_id behavior. The description still adds useful meaning by emphasizing that passing an occurrence's series_id deletes the whole series and by providing a concrete event_id usage example.

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 and resource ('Deletes an event') and clearly distinguishes occurrence deletion from whole-series deletion. It also names the sibling tool to use for declining someone else's meeting, so an agent can separate it from calendar_respond_to_event without opening either schema.

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

Usage Guidelines5/5

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

Explicitly says to use it only when the user asks to cancel or remove the event, and directs the agent to calendar_respond_to_event for declining someone else's meeting. This gives both when-to-use and when-not-to-use guidance with a named alternative.

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

All Prubex tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?