Chronos MCP

bulk_create_journals

Create multiple journal entries at once by providing a calendar UID and JSON array of journal data, with optional parallel execution and mode control.

Instructions

Create 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>",
      "journals_json": "<journals_json>"
    },
    "name": "bulk_create_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
`journals_json`	Yes	JSON array of journal data

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, the description carries full burden. It provides no insight into error handling, partial failures, idempotency, or permission requirements, essential for a bulk mutation operation.

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?

Description is extremely short (5 words). While concise, it lacks necessary qualifying information that would justify its brevity.

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?

Even with an output schema, the description fails to communicate expected return values, possible errors, or aggregate behavior for bulk operations, leaving critical 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 high (83%), so baseline is 3. The description adds nothing beyond schema; no explanation of the journals_json format or how calendar_uid relates to the operation.

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 states the tool creates multiple journal entries in bulk, distinguishing it from single journal creation (create_journal) and other bulk operations by name and scope.

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_journal for single entries or bulk_create_events/tasks, nor any prerequisites or context for its use.

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