Skip to main content
Glama

dietbox_prescription_write

Create a new supplement/herbal medicine prescription (receituário) in Dietbox. For meal plans, see dietbox_meal_plan (read-only).

Campos aceitos pelo DietBox (são TODOS os que a prescrição tem):

  • title (obrigatório): nome da prescrição.

  • patient_id (obrigatório): Id numérico do paciente.

  • date: data da prescrição (ISO, ex.: "2026-11-04"); padrão = hoje.

  • description: o conteúdo da prescrição (suplementos/fitoterápicos, doses, observações), em texto.

  • posology: posologia / modo de uso. Não existe campo de itens estruturados: escreva os itens no description. Não é preciso montar JSON.

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

Input Schema

NameRequiredDescriptionDefault
dataNo
dateNo
titleYes
accountNo
posologyNo
patient_idYes
descriptionNo
patient_idsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • addedInput schema / properties / data / anyOf
      Added value: +[
      +  {
      +    "type": "string"
      +  },
      +  {
      +    "additionalProperties": {},
      +    "propertyNames": {
      +      "type": "string"
      +    },
      +    "type": "object"
      +  }
      +]
    • removedInput schema / properties / data / default
      Removed value: -"{}"
    • removedInput schema / properties / data / type
      Removed value: -"string"
    • addedInput schema / properties / date
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / description
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / posology
      Added value: +{
      +  "type": "string"
      +}
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and idempotentHint=false, so the safety profile is covered. The description adds genuine behavioral context beyond that: the data model constraint that there are no structured item fields and items must be written into description, plus bulk execution via patient_ids. It omits what the response contains and any duplicate/permission behavior.

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, and the field list is cleanly bulleted with required markers. The prose about not needing JSON is slightly redundant with the no-structured-items note, but overall there is little waste.

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 an 8-parameter write tool with no output schema, the description covers the essential data model and bulk mode, which is the main source of misuse risk. It still leaves the account parameter, the `data` parameter, and the return value unexplained, so it is adequate but not complete.

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 0%, so the description must carry parameter meaning. It documents title, patient_id, date, description and posology with useful semantics (ISO date format, default = today, free-text content), and briefly notes patient_ids for bulk. However, the account parameter and the odd `data` property (which accepts object or string) are never explained, and the claim that the listed fields are 'TODOS os que a prescrição tem' under-describes the actual 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?

States a specific verb and resource ('Create a new supplement/herbal medicine prescription (receituário) in Dietbox') and immediately routes a related need to a named sibling ('For meal plans, see dietbox_meal_plan (read-only)'). An agent can distinguish this from dietbox_prescription_get/list/list_models without opening any 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?

Provides clear context (creating prescriptions) and one explicit exclusion pointing to dietbox_meal_plan for meal plans. It does not, however, mention the sibling read tools (dietbox_prescription_get/list) or clarify when to use this versus an existing prescription, so the guidance is good but not exhaustive.

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.