Cronometer MCP

copy_day

Copy all diary entries from one date to another, adding to existing destination entries without removing them; defaults to today and the prior day.

Instructions

Copy all diary entries from one day onto another.

Additive -- does not remove existing entries on the destination date, so running it twice duplicates them.

Args: date: Destination date as YYYY-MM-DD (defaults to today). source_date: Day to copy from, as YYYY-MM-DD. Defaults to the day before the destination.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "copy_day"
  }
}

Input Schema

Name	Required	Description	Default
`date`	No
`source_date`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.1.0Nov 14, 2026

TDQS

A4.3/5.0

Behavior4/5

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

The annotations already declare readOnlyHint=false, destructiveHint=false, and idempotentHint=false, but the description adds concrete meaning to the non-idempotency by explaining that copying is additive and running it twice duplicates entries. That is genuinely useful context beyond the hints, though it says nothing about permissions or what happens if the source day is empty.

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 purpose is front-loaded in one sentence, followed immediately by the most important behavioral caveat, then compact per-argument notes. No sentence is repetitive or padding.

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

Completeness4/5

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

With only two optional parameters and an output schema present, the description covers what an agent needs to invoke the tool correctly, including formats, defaults, and the duplication risk. Minor gaps remain around edge cases such as copying from an empty source day or how conflicts on the destination are handled.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% and both parameters surface as null defaults in the schema, so the description carries the full burden. It documents both parameters, gives the expected YYYY-MM-DD format, and supplies the real effective defaults (today for destination, previous day for source), which the schema does not convey.

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 first sentence gives a specific verb and resource: copying all diary entries from one day to another. That behavior is distinct from the mutation siblings listed (add_food_entry, edit_note, delete_repeat_item), so an agent can identify this tool without opening the schema.

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

Usage Guidelines3/5

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

Usage is implied through the default rules (destination defaults to today, source to the day before), which tells the agent how the tool can be called with no arguments. However, it never states when to prefer this over manually adding entries with add_food_entry, nor any exclusions or prerequisites.

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

Deploy Server