cronometer-mcp

by cphoskins

Overview Schema Source Related Servers Discussions Admin

Python

Remote

get_repeated_items

List all recurring food entries in Cronometer, including food name, quantity, measure, diary group, and repeat days.

Instructions

List all recurring food entries.

Returns all repeat items configured in Cronometer, including their food name, quantity, measure, diary group, and which days of the week they repeat on.

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": "get_repeated_items"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.0.3Mar 21, 2026

TDQS

A4.3/5.0

Behavior4/5

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

No annotations are provided, so the description carries the full burden. It clearly states what the tool returns, which is the key behavioral aspect. It does not disclose non-obvious traits like rate limits or auth, but for a simple list operation it is adequate.

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 well-structured sentences, no wasted words. The first sentence conveys the core purpose, and the second adds necessary detail about return contents.

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

Completeness5/5

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

Given the zero-parameter input and existence of an output schema, the description is complete enough. It lists all relevant return fields, and the sibling tools provide context for this read-only list operation.

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?

The tool has zero parameters, and the input schema is complete (100% coverage). The description adds no parameter information, which is appropriate given the absence of parameters. Baseline for 0 params is 4.

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 'List all recurring food entries' using a specific verb and resource. It also details the returned fields (food name, quantity, etc.), which unambiguously defines the tool's purpose.

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?

No explicit guidance on when to use this tool vs alternatives like add_repeat_item or delete_repeat_item. The usage context is implied by the 'List' verb, but the description does not provide when-not or alternative recommendations.

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