Skip to main content
Glama

dietbox_antropometria_list

Read-onlyIdempotent

Read anthropometric evaluations in Dietbox (weight, height, BMI, body composition). Actions: list (paginated, filter by tipo; requires patient_id), get (by anthropometry_id), get_latest (current measurements for patient_id).

[Flattened action: list]

Bulk support: accepts patient_ids, anthropometry_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_antropometria_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
skipNo
takeNo
tipoNo
accountNo
patient_idYes
patient_idsNo
anthropometry_idNo
anthropometry_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.4/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 fully covered without the description. The description adds pagination behavior and bulk execution support, which is genuine value, but says nothing about default page size, ordering, or what happens when both patient_id and patient_ids are supplied.

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, leading with the resource and domain fields before the action breakdown. The main inefficiency is enumerating get and get_latest actions, which are separate sibling tools, forcing an extra "flattened action" caveat to undo that confusion.

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 read tool with no output schema and zero schema descriptions, the definition covers the essentials an agent needs to make a first call, and return-shape explanation is excused by the absence of an output schema. It falls short on the account/tipo semantics and the required-patient_id-versus-bulk tension, which an agent would have to guess at.

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?

With 0% schema description coverage and 8 parameters, the description must compensate and only partly does: it explains patient_id, tipo filtering, pagination, and the patient_ids/anthropometry_ids bulk arrays. It leaves skip/take semantics, the account parameter, and why anthropometry_id appears on a list action completely undocumented, and it never clarifies whether patient_id remains required when using patient_ids.

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?

The description gives a specific verb and resource ("Read anthropometric evaluations in Dietbox") plus the data domain (weight, height, BMI, body composition), which is clearly distinguishable from agenda, prescription, or prontuario siblings. The "[Flattened action: list]" note resolves the ambiguity created by listing get/get_latest actions inside a tool named _list, though that enumeration still adds noise rather than precision.

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 states the key precondition (requires patient_id) and the filter dimension (tipo), and mentions pagination and bulk batching. However it never routes the agent between this tool and the dedicated dietbox_antropometria_get / dietbox_antropometria_get_latest siblings that exist in the same namespace, so the when-to-use boundary is only implied.

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.