io.github.rwestergren/cronometer-api-mcp

import_recipe

Convert free-text ingredients into a Cronometer recipe. Enter each ingredient on a new line; the server matches foods and converts amounts to grams.

Instructions

Create a recipe from a free-text ingredient list.

Cronometer's "Import Recipe" feature: pass ingredients as plain text, one per line, and the server matches each to a food and converts the amount to grams. No need to call search_foods first.

Prefer this when the user describes ingredients in their own words. Use add_recipe instead when you have exact food_ids and gram weights -- e.g. the user confirmed specific foods from search_foods results.

Matching is fuzzy, so report the returned matches back to the user for confirmation. Unresolved lines are listed under "unmatched" and excluded from the recipe. This saves to My Foods; use add_food_entry to log it.

Args: ingredients: Ingredient lines separated by newlines, e.g. "2 tbsp olive oil\n200g chicken". Include quantities where known, since bare names can match surprising amounts. name: Recipe name. Defaults to a server-generated one.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`name`	No
`ingredients`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Addedv0.2.3Sep 8, 2026

TDQS

A5/5.0

Behavior5/5

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

The description adds significant behavioral context beyond annotations: matching is fuzzy, returned matches should be reported for confirmation, unresolved lines are excluded under 'unmatched,' and the result saves to My Foods. It also clarifies that add_food_entry is needed to log it.

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 front-loaded with the core purpose and every sentence contributes meaningful guidance: usage, alternatives, behavior, and parameter semantics. The Args section is clean and directly aligned with the schema properties.

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?

For a two-parameter tool with an output schema, this description covers input format, optional parameters, matching behavior, persistence, and follow-up action. No important guidance is missing for correct invocation.

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

Parameters5/5

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

Schema description coverage is 0%, but the description fully compensates. It explains that ingredients are newline-separated, gives a concrete example, and warns that bare names can produce surprising amounts. It also clarifies that name defaults to a server-generated value.

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 opens with a specific verb and resource: 'Create a recipe from a free-text ingredient list.' It distinguishes itself from add_recipe and search_foods, making its role among siblings immediately clear.

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

Usage Guidelines5/5

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

Explicitly states when to prefer this tool: 'Prefer this when the user describes ingredients in their own words.' It also names the alternative condition: 'Use add_recipe instead when you have exact food_ids and gram weights,' and even notes that search_foods is unnecessary first.

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