Skip to main content
Glama

dietbox_anamnese_get_latest

Read-onlyIdempotent

Read anamnesis (health history questionnaire) records in Dietbox. Actions: list (paginated, requires patient_id), get (by anamnesis_id), get_latest (most recent for patient_id).

[Flattened action: get_latest]

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>"
    },
    "name": "dietbox_anamnese_get_latest"
  }
}

Input Schema

NameRequiredDescriptionDefault
skipNo
takeNo
searchNo
accountNo
patient_idYes
patient_idsNo
anamnesis_idNo
anamnesis_idsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / required
      Added value: +[
      +  "patient_id"
      +]
  2. First observed

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds useful bulk-execution context (patient_ids/anamnesis_ids batching) but says nothing about what happens on a missing record, how bulk results are ordered/paired to inputs, or how account scoping affects the lookup.

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?

Short and front-loaded: the resource comes first, the action map second, the bulk note last. The only waste is the multi-action preamble retained for a single flattened action, which is defensible as sibling context but not strictly needed here.

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

Completeness2/5

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

With 8 parameters, no output schema, and zero schema description coverage, the definition should explain the return shape (an anamnesis record) and the empty-result behavior. It also leaves the interaction between the bulk id arrays and the single-patient required field unresolved, which matters for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across 8 parameters, so the description must carry the burden and largely does not. It explains patient_id (required), patient_ids and anamnesis_ids (batching), but skip, take, search, account and anamnesis_id have no meaning documented anywhere, and it is unclear which of these actually apply to the get_latest action.

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?

States a specific verb and resource (read anamnesis / health history questionnaire records) and enumerates the three actions, marking that this instance is the flattened get_latest action meaning 'most recent for patient_id'. That distinguishes it from dietbox_anamnese_get and dietbox_anamnese_list, though the leftover action list adds slight noise for a tool that only does one thing.

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

Usage Guidelines3/5

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

The action breakdown implies the selection rule (use list for paginated enumeration with patient_id, get by anamnesis_id, get_latest for the most recent), and it names the required patient_id. It never explicitly states when NOT to use this tool or what to do if the patient has no anamnesis on record, leaving that to inference.

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.