Chronos MCP

bulk_create_events

Create multiple calendar events at once by passing a list of event data dictionaries. Supports validation before execution and different failure modes.

Instructions

Create 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>",
      "events": "<events>"
    },
    "name": "bulk_create_events"
  }
}

Input Schema

Name	Required	Description	Default
`mode`	No	Operation mode: continue, fail_fast	continue
`events`	Yes	List of event data dictionaries
`account`	No	Account alias
`calendar_uid`	Yes	Calendar UID
`validate_before_execute`	No	Validate events before creation

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.1.0Jul 12, 2026

TDQS

B3/5.0

Behavior2/5

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

No annotations are present, so the description must fully disclose behavior. It only states the basic action, omitting side effects, error handling, atomicity, rate limits, or what 'bulk' implies operationally. Minimal transparency.

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 sentence with no redundancy, but it is too brief for the tool's complexity (5 parameters, output schema). Conciseness is achieved at the expense of necessary detail.

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 and the presence of an output schema, the description should explain bulk behavior, error modes, validation, and limits. It only states the basic function, leaving significant gaps.

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 100%, so baseline is 3. The description adds no additional meaning beyond the schema; parameters like 'mode' and 'validate_before_execute' are documented only in the schema.

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 'Create multiple events in bulk' clearly states the verb (create), resource (events), and scope (multiple/bulk). It effectively distinguishes from singleton 'create_event' and sibling bulk operations like 'bulk_delete_events'.

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 versus alternatives like 'create_event' or other bulk tools. No prerequisites, exclusions, or contextual advice provided.

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