Cronometer MCP

set_weekly_macro_schedule

Idempotent

Assign a saved macro template as the default nutrition targets for selected days, updating every future week or resetting chosen days to profile defaults.

Instructions

Make a saved template the default targets on chosen days of the week.

This changes the recurring schedule for every future week.

Args: template_name: A template from list_macro_templates, or "default" to put those days back on the profile's default targets. days: "all", "weekdays", "weekends" or e.g. "Mon,Wed,Fri".

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": {
      "template_name": "<template_name>"
    },
    "name": "set_weekly_macro_schedule"
  }
}

Input Schema

Name	Required	Description	Default
`days`	No		all
`template_name`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.1.0Nov 14, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare non-read-only, idempotent, non-destructive behavior, so the bar is lower, and the description still adds a real behavioral fact: the change applies to 'every future week', i.e. it is a recurring-scope mutation rather than a single-day edit. It does not say whether days omitted from the call are left untouched or cleared, which is the main remaining ambiguity.

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?

Two front-loaded sentences establish the action and its recurring scope before the Args block, and every line earns its place by resolving either a parameter format or a reset case. No filler or restatement of the tool name.

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?

An output schema exists, so return values need not be described, and the two-parameter surface is small enough that the definition covers what an agent needs to invoke it. The one unresolved point is overwrite-versus-merge semantics for days not named in the call.

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?

Schema description coverage is 0%, so the description must carry the parameter burden and largely does: it explains template_name's source and its 'default' sentinel meaning, and it enumerates accepted day formats ('all', 'weekdays', 'weekends', 'Mon,Wed,Fri'). The only gap is that the default value 'all' is not restated or its effect spelled out.

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 first sentence gives a specific verb and resource ('Make a saved template the default targets') plus a scoping dimension ('on chosen days of the week'), which distinguishes it from a one-off target edit. It does not explicitly name or contrast with the sibling set_macro_targets, so the differentiation is implicit rather than stated.

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

Usage Guidelines4/5

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

It tells the agent where templates come from ('A template from list_macro_templates') and documents the special reset path via template_name='default'. What is missing is an explicit statement of when to choose this over set_macro_targets for non-recurring changes, so the guidance is clear but not fully comparative.

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

Deploy Server