Skip to main content
Glama

dietbox_antropometria_get_latest

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

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

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

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description still adds real information beyond them: the bulk path (patient_ids / anthropometry_ids for batched execution) and the measurement fields returned. Pagination is only mentioned as belonging to the list action, and nothing is said about what happens when a patient has no evaluations.

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?

Short and front-loaded, but a sizeable share of the text documents actions (list, get) that this flattened tool does not expose, forcing the agent to filter noise. The '[Flattened action: get_latest]' marker is machine scaffolding rather than useful prose. What remains is efficient.

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 no parameter descriptions, the definition is only partially sufficient: it never defines pagination controls, the tipo filter, or the account parameter, nor any error behavior for missing anthropometry records. Reading the tool name plus this text, an agent still could not confidently construct calls that use skip/take/tipo.

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?

Schema description coverage is 0%, so the description must carry the semantics and it only partially does: it explains patient_id, anthropometry_id, patient_ids and anthropometry_ids. Four parameters — skip, take, tipo and account — are never mentioned, including the take default of 50 and what 'tipo' filters. Half the surface is undocumented, so the baseline for a zero-coverage 8-param schema is not met.

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 concrete verb and resource ('Read anthropometric evaluations in Dietbox') and enumerates the data returned (weight, height, BMI, body composition). It also names the sibling actions (list, get, get_latest) and marks which one this tool is, so an agent can separate it from dietbox_antropometria_list and dietbox_antropometria_get. Minor deduction because the description spends most of its text on the other two actions that this tool cannot perform.

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?

Provides a de-facto routing rule by binding each action to its identifying parameter: get by anthropometry_id, get_latest for current measurements by patient_id, list requires patient_id. That is enough for an agent to pick correctly among the antropometria siblings. It stops short of an explicit when-not statement (e.g., 'use dietbox_antropometria_list if you need history').

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.