Skip to main content
Glama

dietbox_agenda_write

Create a new event/appointment in the Dietbox agenda.

  • start / end: data e hora ISO. Sem offset (ex.: "2026-04-16T14:00:00") o horário é lido no fuso de timezone (padrão America/Sao_Paulo); com offset (ex.: "-03:00") vale o instante informado.

  • tipo: "consulta" (padrão) ou "outros". Para outro tipo do DietBox (ex.: retorno), envie o código numérico em tipo_codigo; descubra o código lendo o campo Type de um evento desse tipo no dietbox_agenda (action=list).

  • patient_id: Id numérico do paciente (use dietbox_patient_list (campo Id do paciente) para obter o id).

  • titulo, descricao: título e observações do evento.

  • local_atendimento: Id do local de atendimento (campo IdLocalAtendimento de um evento existente), quando a nutricionista tem mais de um local.

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": {
      "start": "<start>",
      "end": "<end>"
    },
    "name": "dietbox_agenda_write"
  }
}

Input Schema

NameRequiredDescriptionDefault
endYes
tipoNoconsulta
startYes
onlineNo
tituloNo
accountNo
timezoneNoAmerica/Sao_Paulo
todo_diaNo
descricaoNo
patient_idNo
patient_idsNo
tipo_codigoNo
local_atendimentoNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / local_atendimento
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / online
      Added value: +{
      +  "type": "boolean"
      +}
    • addedInput schema / properties / tipo_codigo
      Added value: +{
      +  "type": "number"
      +}
  2. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnly=false, destructive=false, idempotent=false, so the mutation profile is known. The description adds genuinely useful behavior beyond that: the timezone interpretation rule for offset vs offset-less timestamps, the `tipo` default, and the existence of bulk execution. However, it never explains what bulk actually does (one event per patient_id?), how `patient_ids` interacts with `patient_id`, or how conflicts/duplicates are handled.

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 in one sentence, then parameters are broken into scannable bullets with a trailing bulk note. Most sentences carry real information (the timezone rule especially); the 'Bulk support' line is a one-liner that under-delivers relative to the space it occupies.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 13-parameter, non-idempotent calendar mutation with no output schema and zero schema descriptions, the definition covers creation and timezone semantics well but omits recurring behavior (`todo_dia`), the `online` flag, `account` scoping, and the result of a bulk call. An agent could invoke it, but it would be guessing on several inputs.

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 description coverage is 0%, so the description must carry the load, and it does for the critical parameters: the offset/no-offset rule for `start`/`end`, the `consulta` default and numeric-code escape hatch for `tipo`, the source of `patient_id`, and the meaning of `local_atendimento`. It leaves `online`, `todo_dia` (presumably recurrence), and `account` completely undefined, which is a material gap for 13 parameters.

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?

Opens with a specific verb+resource: 'Create a new event/appointment in the Dietbox agenda.' It also names the read path (`dietbox_agenda` with action=list) as the discovery route, so an agent distinguishes this write tool from the agenda read/summary siblings without inspecting schemas.

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?

Gives concrete pre-call guidance: use `dietbox_patient_list` to obtain the numeric patient Id, read the `Type` field of an existing event via `dietbox_agenda` (action=list) to find a `tipo_codigo`, and only set `local_atendimento` when the nutritionist has multiple locations. It stops short of stating when to prefer this over other scheduling/creation paths or what to do when an appointment already exists.

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.