Cronometer MCP

delete_macro_template

DestructiveIdempotent

Deletes a saved macro target template by its template ID. Use the ID from list_macro_templates to remove outdated nutrition targets from your Cronometer account.

Instructions

Delete a saved macro target template.

Args: template_id: From list_macro_templates.

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_id": "<template_id>"
    },
    "name": "delete_macro_template"
  }
}

Input Schema

Name	Required	Description	Default
`template_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

B3.2/5.0

Behavior2/5

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

Annotations already declare destructiveHint=true, idempotentHint=true and openWorldHint=true, so the safety profile is fully covered by structured data. The description adds no behavior beyond that — it does not say whether removal is permanent, whether existing macro targets derived from the template are affected, or what a repeat call returns. With annotations carrying the load the bar is lower, but there is essentially no added context here.

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?

The purpose sentence is front-loaded and the argument note is short and actionable. The 'Args:' framing is slightly verbose for one parameter but nothing is wasted.

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?

For a single-argument destructive tool with an output schema and rich annotations, the description covers what it deletes and where to get the ID. It omits the consequences of deletion and any permission requirements, which matters for an irreversible mutation.

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

Parameters3/5

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

Schema coverage is 0% for the single parameter ('Template Id', integer), so the description must compensate, and it partially does by telling the agent to obtain the value from list_macro_templates. It gives no format, validity, or error behavior detail beyond that.

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 description uses a specific verb and resource ('Delete a saved macro target template'), which is unambiguous and distinguishable from sibling resources like delete_fast or delete_repeat_item. It stops short of explicitly contrasting with those siblings, but the resource name does most of the work.

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 only implied by 'Delete' — the agent infers this is for removing a template it no longer wants. The one real guideline given is provenance for the argument ('From list_macro_templates'), which usefully points to the discovery step. There is no statement of preconditions or when not to use it.

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

Deploy Server