Skip to main content
Glama

Meals of a day

zarok_get_meals
Read-onlyIdempotent

Returns the meal program for one date (YYYY-MM-DD): the program start and length, and the meals of that day with their keys, times, items and repeat rule. Supplement lists are not included. Use the meal keys from here in create_meal, update_meal and delete_meal operations. Read-only.

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

Input Schema

NameRequiredDescriptionDefault
dateYesA calendar date in the user’s local time, YYYY-MM-DD

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / date / description
      Added value: +"A calendar date in the user’s local time, YYYY-MM-DD"
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive behavior. The description adds useful behavioral context beyond that: the return shape, the exclusion of supplement lists, and the intended reuse of meal keys in mutation tools.

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?

The description is a compact paragraph with the core purpose front-loaded, followed by return details, exclusions, and intended downstream use. There is no wasted text.

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 adequately explains what is returned: program start and length, meals with keys/times/items/repeat rule, and that supplement lists are omitted. This is complete enough for an agent to call and interpret the tool.

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 coverage is 100%, and the single date parameter is already fully described in the schema with format and local-time semantics. The description restates the YYYY-MM-DD format but adds no additional parameter meaning beyond the schema.

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?

The description states a specific verb and resource (returns the meal program), scope (one date), and return contents (program start/length, meals with keys, times, items, repeat rule). It is clearly distinguishable from sibling retrieval tools like get_plan or get_week_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?

It gives clear context: use this for a single day's meal program, supplement lists are excluded, and meal keys are intended for create/update/delete operations. It does not, however, compare against sibling retrieval tools such as get_plan or get_week_summary, so routing guidance is not fully explicit.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources