cronometer-mcp

by cphoskins

Overview Schema Source Related Servers Discussions Admin

Python

Remote

set_day_complete

Mark any diary date as complete or incomplete to reflect whether nutrition tracking for that day is finished.

Instructions

Mark a diary day as complete or incomplete.

Args: date: Date to mark as YYYY-MM-DD. complete: True to mark complete, False to mark incomplete.

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": {
      "date": "<date>"
    },
    "name": "set_day_complete"
  }
}

Input Schema

Name	Required	Description	Default
`date`	Yes
`complete`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.0.3Mar 21, 2026

TDQS

A3.8/5.0

Behavior3/5

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

The description explains the basic behavior (toggle complete/incomplete) but does not disclose any side effects, permissions, or return values. Since no annotations are provided, the description carries the full burden, but it is adequate for a straightforward toggle operation.

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 description is concise, consisting of one line for purpose and two lines for parameters. It is well-structured with no extraneous information.

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?

Given the tool's simplicity and the presence of an output schema (not shown), the description covers the essential purpose and parameters. It does not explain downstream effects, but for a toggle operation, this is acceptable.

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

Parameters4/5

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

With 0% schema description coverage, the description adds crucial meaning: it specifies the date format (YYYY-MM-DD) and clarifies the boolean parameter's effect ('True to mark complete, False to mark incomplete'). This compensates well for the empty 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 clearly states the action: 'Mark a diary day as complete or incomplete.' This is a specific verb-resource pair, and it distinguishes this tool from siblings like add_food_entry or cancel_active_fast.

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, such as copy_day or set_macro_targets. It lacks context about prerequisites or scenarios where marking a day complete is appropriate.

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