Skip to main content
Glama

dietbox_meal_plan

Read-onlyIdempotent

Get the active meal plan (plano alimentar) for a patient in Dietbox. Returns the full list of meals with foods, portions, schedule, and day-of-week assignments. Each meal has: title (e.g. "Café da manhã"), time, text (food items with portions), observacao, and weekday flags.

NOTE: This is different from "prescriptions" — prescriptions in Dietbox are supplement/herbal medicine prescriptions. Use this tool for food/meal plans.

READ-ONLY (LIMITAÇÃO DO DIETBOX): a API v2 do Dietbox só oferece LEITURA do plano alimentar (GET /plano-alimentar/{paciente}); criar e editar plano, assim como a biblioteca de receitas, existem apenas nas telas internas do site do Dietbox, sem API. Por isso não existe dietbox_meal_plan_write nem ferramenta de receitas. Para criar/editar planos e receitas, use o site do Dietbox.

Bulk support: accepts patient_ids for batched execution.

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": {
      "patient_id": "<patient_id>"
    },
    "name": "dietbox_meal_plan"
  }
}

Input Schema

NameRequiredDescriptionDefault
accountNo
patient_idYes
patient_idsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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 readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered structurally. The description adds genuinely non-obvious context: the read-only nature is an API limitation of Dietbox v2, not a design choice, and no dietbox_meal_plan_write or recipe tool exists. It stops short of describing behavior when a patient has no active plan, so it is not exhaustive.

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?

Content is front-loaded: capability, then return shape, then disambiguation, then limitation, then bulk note. Every block carries information, though the all-caps Portuguese LIMITAÇÃO parenthetical restates the same read-only point in two languages, adding some redundancy.

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 correctly compensates by enumerating the returned meal fields (title, time, text, observacao, weekday). What remains missing is the empty-state behavior (no active plan) and the undocumented account parameter, both relevant for a 3-parameter tool at 0% schema coverage.

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 0%, so the description carries the burden, and it only partially does so — it explains that patient_ids enables batched execution, which is real added meaning. However, the account parameter is never mentioned, and the relationship between the required patient_id and the optional patient_ids (precedence, mutual exclusivity, whether both can be sent) is left unstated.

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 ("Get the active meal plan for a patient") and immediately names the fields returned (meals, foods, portions, schedule, weekday flags). It also explicitly separates itself from dietbox_prescription_* by disambiguating the term "prescriptions" — a distinction an agent could not infer from names alone.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit routing guidance: use this for food/meal plans, not prescriptions. It further explains that no write counterpart exists and that creating/editing plans must happen on the Dietbox website, which pre-empts an agent searching for a non-existent write tool.

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.