Cronometer MCP

nutrient_report

Read-onlyIdempotent

Compare every tracked nutrient for a day against its target, including amount, upper limit, and percent of target, sorted lowest first to spot gaps and excesses.

Instructions

Every tracked nutrient for a day against its target: amount, target, upper limit and percent of target, lowest first.

Good for spotting gaps (what to eat more of) and anything over a limit.

Args: date: YYYY-MM-DD (defaults to today).

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

Input Schema

Name	Required	Description	Default
`date`	No

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 readOnlyHint, idempotentHint and destructiveHint=false, so safety is covered. The description adds real behavioral detail beyond that: results are sorted lowest-first and each row carries an upper limit alongside the target, which shapes interpretation. It doesn't discuss pagination or partial-day behavior, but with a rich annotation set and an output schema this is solid.

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?

Front-loaded with the resource and returned fields, then one sentence on interpretation, then the arg. Three compact pieces, none wasted.

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?

Output schema exists so return values needn't be explained, annotations cover safety, and the single parameter is fully specified. The only shortfall is not positioning it against the closely-named nutrition siblings in this catalog.

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 coverage is 0% on the single date parameter, so the description must carry the load, and it does: format YYYY-MM-DD and the meaning of the null default (today). That resolves the ambiguity the schema leaves (default: null). A 4 rather than 5 only because there is nothing else to document.

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 opens with a specific verb+resource+scope: every tracked nutrient for a day measured against its target, including amount, target, upper limit and percent. That is materially different from a generic daily-nutrition fetch. It stops short of naming which sibling to use instead (e.g. get_daily_nutrition or analyze_day), so it isn't a 5.

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 gives clear when-to-use context: spotting nutrient gaps and finding values over a limit. There are no explicit exclusions or named alternatives despite several overlapping siblings, so it falls short of 5.

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

Deploy Server