Vitalli

joiva_share_meal

Create an anonymous, time-limited link to one meal. entryIds are log entry ids of one meal (the day view groups them per meal in meals). Unlike a day link, the set of entries is frozen: nothing logged afterwards shows up in it. The returned URL appears only in this reply and cannot be retrieved again.

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": {
      "entryIds": "<entryIds>",
      "date": "<date>"
    },
    "name": "joiva_share_meal"
  }
}

Input Schema

Name	Required	Description
`tz`	No	IANA timezone, default Europe/Berlin
`date`	Yes	YYYY-MM-DD the meal belongs to
`entryIds`	Yes	The log entry ids to share, all from the same meal
`ttlHours`	No	Validity in hours (1 to 2160 = 90 days). Default: 168 = 7 days.
`mealLabel`	No	Headline of the shared page, e.g. 'Mittagessen'

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 4, 2026

changedInput schema / properties / entryIds / description

Previous value: -"The entries to share (ids from joiva_get_day), all from the same meal"New value: +"The log entry ids to share, all from the same meal"

First observedOct 27, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Adds context beyond the annotations: the link is anonymous, the entry set is frozen against later logging, and the URL is returned once and never retrievable again — a crucial one-shot consequence that supports the idempotentHint=false signal. It would be stronger if it said how to revoke or list created shares.

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?

Three tight sentences, front-loaded with purpose, then the entry-set semantics, then the irreversibility warning. No filler.

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?

With no output schema, the description carries the return-value burden and does so by stating the URL appears only in the reply. Remaining gap is the share-management lifecycle (listing, revoking), which matters for a tool that creates a persistent artifact.

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, but the description adds real meaning by explaining that entryIds are log entry ids grouped per meal in the day view, which is not obvious from the schema's 'all from the same meal' phrasing.

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 and resource ('Create an anonymous, time-limited link to one meal') and explicitly contrasts with the sibling joiva_share_day by noting the entry set is frozen. An agent can select it without opening the schema.

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?

The 'Unlike a day link' contrast gives a clear condition for choosing this over the day-share alternative, but it never mentions the share lifecycle siblings (joiva_list_shares, joiva_revoke_share) for follow-up or cleanup.

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?