Vitalli

joiva_get_day

Read-onlyIdempotent

Get the signed-in user's Joiva food log for one day. Defaults to today. The default answer is compact: each entry carries id, foodItemId, food, brand, grams, meal, loggedAt, kcal and macros (fields without a value are left out; naehrwertStatus appears only when the nutrient values are not complete yet). The day totals are complete, including micronutrients; coverage gives target, percent and status per nutrient; meals groups the entry ids per meal; plannedEntries are listed the same way, and plannedTotals, forecastTotals (= totals + planned) and forecastCoverage appear when something is planned. detail: 'full' returns the full breakdown per entry: micronutrients, microsOrigin (per nutrient: eigen = from the label/product source, uebernommen = inherited from the generic food, scaled where it depends on fat/carbs/protein, zubereitung = adjusted for the preparation, geschaetzt = estimated), garung, behandlung, notiz as eaten, produktGarung as bought, recipe and portions. entryIds returns only those entries with their full breakdown. Every food carries brand and certifications (bio, demeter, bioland, naturland, fairtrade; left out = none known), which tell products of different makers apart.

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

Input Schema

Name	Required	Description
`tz`	No	IANA timezone, default Europe/Berlin
`date`	No	YYYY-MM-DD
`detail`	No	compact (default): per entry name, brand, amount, meal, time, kcal and macros. full: the complete breakdown per entry.
`entryIds`	No	Entry ids from the compact answer whose full breakdown is returned; other entries are left out.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 4, 2026

changedInput schema / properties / entryIds / description

Previous value: -"Entry ids (from a compact joiva_get_day) whose full breakdown is returned; other entries are left out."New value: +"Entry ids from the compact answer whose full breakdown is returned; other entries are left out."

First observedOct 27, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior. The description adds substantial context beyond that: empty fields are omitted, naehrwertStatus appears only when nutrients are incomplete, forecast fields appear only when something is planned, and detail:'full' returns a specific breakdown.

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?

Purpose is front-loaded and the dense return-value detail is mostly justified because there is no output schema. Some sentences are very long and pack many field names, but they are structured and earn their place.

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?

With no output schema, the description carries the burden of explaining returns and does so thoroughly: compact vs full, totals, coverage, planned/forecast fields, entryIds, and certifications. Combined with annotations and full schema coverage, an agent has enough information to call it correctly.

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 100%, so the baseline is 3; the description nevertheless adds real meaning for detail and entryIds, including what the full breakdown contains and that other entries are excluded. It adds less for tz/date beyond the 'today' default, but overall exceeds the schema baseline.

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?

States a specific verb ('Get') and resource ('signed-in user's Joiva food log for one day'), with the 'one day' scope distinguishing it from range-oriented siblings such as joiva_get_range_summary.

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?

Explains the default (today) and the main mode switches (detail, entryIds), giving clear context for single-day retrieval. It does not explicitly name alternatives or state when not to use it, such as using joiva_get_range_summary for multi-day summaries.

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

All Vitalli tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?