Chronos MCP

bulk_delete_events

Delete multiple calendar events at once by specifying the calendar and list of event UIDs.

Instructions

Delete multiple events in bulk

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_uid": "<calendar_uid>",
      "event_uids": "<event_uids>"
    },
    "name": "bulk_delete_events"
  }
}

Input Schema

Name	Required	Description	Default
`mode`	No	Operation mode	continue
`account`	No	Account alias
`parallel`	No	Execute operations in parallel
`event_uids`	Yes	List of event UIDs to delete
`request_id`	No
`calendar_uid`	Yes	Calendar UID

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.1.0Jul 12, 2026

TDQS

C2.8/5.0

Behavior2/5

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

With no annotations provided, the description carries full responsibility for behavioral disclosure. It only states the basic operation (deleting events) but reveals nothing about error handling, partial failures, authorization requirements, side effects, or return value (despite an output schema existing). This is insufficient for safe autonomous use.

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

Conciseness3/5

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

The description is a single short sentence, making it concise. However, it does not 'earn its place' by providing additional value beyond the obvious. For a tool with six parameters and an output schema, a slightly expanded description would improve clarity without sacrificing conciseness.

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?

Given the tool's complexity (bulk operation, six parameters, output schema) and absence of annotations, the description is far from complete. It fails to explain bulk semantics (atomic vs partial), expected results, or error scenarios. The output schema exists but is not referenced, leaving the agent uninformed about return values.

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?

The input schema already describes 83% of parameters with meaningful descriptions. The tool description adds no additional semantic context beyond what the schema provides, meeting the baseline expectation but not exceeding it.

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 identifies the verb 'Delete', the resource 'events', and the bulk operation. It implicitly distinguishes from 'delete_event' which handles single events, but does not explicitly contrast with other bulk delete tools for journals or tasks. Overall, it's specific enough for an agent to understand the tool's primary function.

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?

The description provides no guidance on when to use this tool versus alternatives such as 'delete_event' for single deletions or other bulk delete tools. There are no usage context, prerequisites, or exclusion criteria, leaving the agent without decision support.

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