Skip to main content
Glama

dietbox_anamnese_write_update

Create or update an anamnesis (health history questionnaire) in Dietbox. Actions:

  • create: cria nova anamnese. Obrigatório: patient_id. Opcional: descricao (título; default "Anamnese"), texto_livre (HTML; quando informado a anamnese é do tipo texto livre), data (ISO), overrides (campos da anamnese, ex.: {IsSmoking:true, HasDiabetes:true, Medicines:"Losartana", FoodAllergies:"camarão", Notes:"..."}; os nomes antigos fuma, diabetes, medicamentos, alergias, observacao também valem).

  • update: atualiza uma anamnese existente. Obrigatório: anamnesis_id E patient_id (o DietBox exige o paciente também na atualização). A anamnese é regravada inteira: envie todos os campos que devem continuar preenchidos (leia antes com dietbox_anamnese action=get). Retorna { id } da anamnese criada/atualizada.

[Flattened action: update]

Bulk support: accepts patient_ids, anamnesis_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>",
      "anamnesis_id": "<anamnesis_id>"
    },
    "name": "dietbox_anamnese_write_update"
  }
}

Input Schema

NameRequiredDescriptionDefault
dataNo
tipoNo
accountNo
descricaoNo
overridesNo
patient_idYes
patient_idsNo
texto_livreNo
anamnesis_idYes
anamnesis_idsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • removedInput schema / properties / anamnesis_id / default
      Removed value: -""
    • removedInput schema / properties / anamnesis_ids / items / default
      Removed value: -""
    • addedInput schema / required
      Added value: +[
      +  "patient_id",
      +  "anamnesis_id"
      +]
  2. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Adds real value beyond the annotations: the record is rewritten in full, so omitted fields are lost, and it states the return shape { id } plus bulk support. However, presenting this as a create/update tool when the schema requires both patient_id and anamnesis_id contradicts the stated 'create: Obrigatório: patient_id' contract, and with destructiveHint=false the omission of any warning that partial payloads silently blank fields is notable even though full-rewrite semantics are stated.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Action-bulleted and front-loaded, but roughly half the text describes the create action that this flattened tool does not expose, and the English/Portuguese mixing plus parenthetical caveats make it heavier than needed.

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?

For a 10-parameter mutation with no output schema, it covers the destructive full-rewrite behavior, the return value, and batch support. Gaps remain on the undocumented tipo/account parameters and on error behavior when anamnesis_id is invalid.

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 0%, so the description must carry the load, and it does for the important ones: patient_id, anamnesis_id, descricao (default title), texto_livre (HTML, switches type), data (ISO), and a detailed overrides map with field names and legacy aliases. Four parameters (tipo, account, data_not provided elsewhere, and the bulk patient_ids/anamnesis_ids arrays beyond a one-line mention) remain under-explained.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Opens with a specific verb and resource: create/update an anamnesis (health history questionnaire), and the '[Flattened action: update]' marker pins the actual operation. The lingering 'create' branch muddies scope, since a separate sibling (dietbox_anamnese_write_create) exists, but the update section clearly states what this call does.

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?

Explicit prerequisites: patient_id AND anamnesis_id for update, plus the instruction to read first with dietbox_anamnese action=get. It does not explicitly say 'use the create sibling instead when no anamnesis_id exists', which is the main missing routing rule given the overlapping siblings.

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.