Chronos MCP

bulk_delete_journals

Delete multiple journal entries in bulk from a CalDAV calendar by providing a list of journal UIDs.

Instructions

Delete multiple journal entries 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>",
      "journal_uids": "<journal_uids>"
    },
    "name": "bulk_delete_journals"
  }
}

Input Schema

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

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.1.0Jul 12, 2026

TDQS

B3.2/5.0

Behavior2/5

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

No annotations provided. Description does not disclose behavioral traits like irreversibility, partial failure handling, or required permissions. Minimal info beyond basic action.

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?

Single short sentence with no unnecessary words. Efficiently conveys core purpose.

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?

Despite presence of output schema and 6 parameters, description lacks details on return values, error conditions, or batch behavior. Incomplete for a bulk operation.

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 coverage is 83% (5 of 6 params described in schema). Description adds no value beyond schema. Baseline 3 applies.

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?

Description clearly states the verb 'delete' and resource 'multiple journal entries', and the term 'bulk' distinguishes it from the single delete sibling tool.

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?

No guidance on when to use this tool vs 'delete_journal' or other alternatives. No context about prerequisites, permissions, or scenarios.

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