Skip to main content
Glama

dietbox_anamnese_get

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]

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": {
      "anamnesis_id": "<anamnesis_id>"
    },
    "name": "dietbox_anamnese_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
skipNo
takeNo
searchNo
accountNo
patient_idNo
patient_idsNo
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: +[
      +  "anamnesis_id"
      +]
  2. First observed

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so safety is covered by structured data. The description adds context the annotations cannot: pagination on the list action and bulk execution via patient_ids/anamnesis_ids. It does not describe pagination defaults or what an empty result looks like.

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?

The text is short and front-loaded: resource and read-only nature first, then the action breakdown, then bulk support. The '[Flattened action: get]' artifact and the enumeration of actions not exposed on this tool are slight noise, but nothing is padded.

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?

For an 8-parameter tool with no output schema and zero schema description coverage, the description is thin — it omits the meaning of pagination/search/account parameters and how skip/take interact with the results. Bulk behavior is mentioned but not bounded (result shape, limits, partial failures).

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 carries the full burden. It explains anamnesis_id for get, patient_id for list, and the bulk patient_ids/anamnesis_ids arrays, but says nothing about skip, take, search, or account — four parameters left entirely undocumented anywhere.

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

Purpose3/5

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

The description names a specific resource (anamnesis / health history records) and a read verb, and enumerates three actions with their key requirement. However, it is a flattened parent-tool description: only 'get' is actually active here (required anamnesis_id), while the 'list' and 'get_latest' actions it describes have dedicated sibling tools. This leaves some ambiguity about which tool an agent is actually holding.

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?

Usage is implied by the action breakdown — 'get (by anamnesis_id)' and 'list (paginated, requires patient_id)' tell the agent what each mode needs. But there is no explicit routing to dietbox_anamnese_list or dietbox_anamnese_get_latest, and no when-not-to-use guidance, which matters given three overlapping anamnesis read tools.

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.