Skip to main content
Glama
Sign In

Vitalli

by app.vitalli.mcp
OverviewDiscussionsAdmin

joiva_get_meal_planning_context

Read-onlyIdempotent

Meal-planning briefing for the signed-in user in one call: allergies and intolerances, active conditions and medications, the 14-day Bristol stool-form trend with pre-written food suggestions, latest biomarkers with their dates, active symptoms (Vora); the current fasting window (Still); the supplements logged today (Stackwell); the day's macros and micronutrient intake gaps, the pantry incl. staples, the shopping list and frequently logged foods (Joiva); body data and energy need (Vitalli). Each source is read only if the user enabled that app for AI access. Every source carries available and fetchedAt, and an error when it is unavailable (not enabled, or not reachable); an unavailable source means unknown, not empty. The guidance field holds fixed notes on reading the data (allergies and a running fast as constraints, intake gaps versus measured values). Personal food rules are not included.

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_meal_planning_context"
  }
}

Input Schema

NameRequiredDescriptionDefault
tzNoIANA timezone, default Europe/Berlin
dateNoYYYY-MM-DD for the Joiva day state. Defaults to today.
sectionsNoLimit the briefing to these sources. Default: all sources.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior5/5

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

Beyond the read-only/idempotent annotations, the description discloses important runtime behavior: each source is read only if enabled for AI access, each source carries available and fetchedAt plus an error when unavailable, and an unavailable source means unknown rather than empty. It also explains the fixed guidance field and distinguishes what is excluded, which materially helps correct interpretation.

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 description is long but appropriately dense for a complex multi-source briefing, and it is front-loaded with the core purpose. The semicolon-separated source list is efficient though somewhat run-on, which keeps it from a top score.

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?

This is a complex aggregate tool with no output schema, and the description compensates by listing the included sources and explaining the availability/error fields and guidance semantics. An agent has enough context to call it and interpret unavailable data correctly.

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 description coverage is 100%, and the schema already documents tz, date, and sections including defaults. The description does not add parameter-specific syntax or default behavior beyond the schema, so the baseline of 3 applies.

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 identifies a specific retrieval: a consolidated meal-planning briefing for the signed-in user, and it enumerates the source domains and data included. That makes the scope clear, but it does not explicitly contrast itself with narrower sibling getters such as joiva_get_day or vora_get_health_profile, so it falls short of perfect sibling differentiation.

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?

The phrase "in one call" implies this is the consolidated-context tool, and the description gives a useful boundary by noting that personal food rules are not included. However, it does not explicitly say when to use this tool instead of the many narrower sibling tools, so the guidance is only implied.

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

All Vitalli toolsInspect
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