Skip to main content
Glama

dietbox_anamnese_list

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: list]

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_list"
  }
}

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/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. The description adds genuinely new behavior: list results are paginated and bulk execution is supported via patient_ids/anamnesis_ids. It stops short of stating default page size, maximum batch size, or ordering, which would matter for a batched read.

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 description is short and front-loads the resource and action list, then the flattened-action marker and bulk note. The action enumeration is slightly redundant for a single-action tool, but no sentence is wasted.

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?

With 8 parameters, no schema descriptions, and no output schema, the definition should say more about pagination controls and what a record contains. It does cover the required key and bulk mode, which are the main decision points, but the pagination/search inputs and the absence of any return-shape hint leave gaps.

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, yet it only clarifies patient_id, patient_ids, anamnesis_id and anamnesis_ids. The pagination and search parameters (skip, take, search) and the account parameter are never mentioned, so half the inputs remain semantically opaque.

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 says "Read anamnesis (health history questionnaire) records" and then enumerates three actions (list, get, get_latest), with "[Flattened action: list]" clarifying which one this tool exposes. The verb+resource is identifiable, but describing three actions in a tool that only performs list blurs the purpose, and it never distinguishes itself from the sibling dietbox_anamnese_get / dietbox_anamnese_get_latest tools.

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?

It implies routing rules by tagging each action with its key ("list ... requires patient_id", "get (by anamnesis_id)", "get_latest ... for patient_id"), so an agent can infer this tool is for patient-scoped listing. However, it never names the sibling tools as alternatives or states when NOT to use this one, leaving the routing 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.