Cronometer MCP

fetch

Read-onlyIdempotent

Retrieve full details for a searched food's nutrients or a specific diary day using an ID from search results.

Instructions

Read one search result in full: a food's nutrients, or a diary day.

Args: id: An id from search, "food:" or "diary:".

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": {
      "id": "<id>"
    },
    "name": "fetch"
  }
}

Input Schema

Name	Required	Description	Default
`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.6/5.0

Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description adds that the return payload is the full record for exactly one item, which is genuine added context, but says nothing about failure behavior for malformed ids or the effect of an open-world lookup.

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?

One front-loaded sentence states purpose and payload, followed by a compact Args block for the one parameter. There is no filler, though the Args block adds little structural value for a single parameter that could have been folded into the sentence.

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?

The tool is simple (one required string) and an output schema exists, so return-value explanation is unnecessary; purpose and id format are both stated. The only real gap is relationship guidance toward sibling detail tools, which matters given the overlap with get_food_details and get_food_log.

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 single parameter entirely and it does: it specifies the two id grammars, "food:<id>" and "diary:<YYYY-MM-DD>", including the date format. That is meaningful meaning beyond the bare string-typed "Id" in the schema, missing only what to do when the prefix is omitted or unrecognized.

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?

"Read one search result in full: a food's nutrients, or a diary day" pairs a specific verb with a specific resource and names the two entity types returned. It is clear what the call does, though it never distinguishes itself by name from overlapping siblings such as get_food_details or get_food_log.

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?

"Read one search result" plus "An id from search" implies the workflow (search first, then fetch) and the id format, which is useful implied guidance. There is no explicit when-not guidance, no statement on invalid or expired ids, and no routing to the sibling detail tools that could serve similar needs.

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

Deploy Server