Cronometer MCP

remove_note

DestructiveIdempotent

Deletes a diary note by note ID from your Cronometer food log. Use it to remove outdated or incorrect notes and confirm the deletion against the note's date.

Instructions

Delete a note from the diary.

Args: note_id: The noteId, from get_food_log. date: The note's day, YYYY-MM-DD (defaults to today); used to confirm it went.

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": {
      "note_id": "<note_id>"
    },
    "name": "remove_note"
  }
}

Input Schema

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

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.1.0Nov 14, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so the safety profile is conveyed structurally. The description adds a small amount of behavioral context with 'used to confirm it went,' suggesting a verification purpose, but says nothing about irreversibility, confirmation requirements, or failure behavior for a destructive operation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the action, then a compact Args block with no wasted prose. The phrasing 'used to confirm it went' is slightly informal but still communicates intent in minimal space.

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

Completeness3/5

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

Output schema exists, so return values need not be described. For a destructive, open-world delete with only one required parameter, the definition is close to complete, but it omits what happens when the note is missing or whether the deletion is permanent — relevant context for a destructiveHint=true tool.

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 parameters, and it does: note_id is documented with its source (get_food_log) and date with its format (YYYY-MM-DD) plus a stated default of today. The only weakness is a mild mismatch with the schema, which declares date default null rather than today.

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?

States a specific verb and resource: 'Delete a note from the diary.' The delete vs. add_note/edit_note distinction is inferable from the verb, but the definition never explicitly contrasts itself with those siblings.

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?

Provides useful provenance guidance by telling the agent to obtain note_id from get_food_log, which implies the call happens after reading the log. However, there is no explicit when-to-use/when-not guidance, no mention of edit_note as the alternative for modifying rather than removing, and no note about what to do if the note does not exist.

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

Deploy Server