Skip to main content
Glama

dietbox_antropometria_get

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]

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": {
      "anthropometry_id": "<anthropometry_id>"
    },
    "name": "dietbox_antropometria_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
skipNo
takeNo
tipoNo
accountNo
patient_idNo
patient_idsNo
anthropometry_idYes
anthropometry_idsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • removedInput schema / properties / anthropometry_id / default
      Removed value: -""
    • removedInput schema / properties / anthropometry_ids / items / default
      Removed value: -""
    • addedInput schema / required
      Added value: +[
      +  "anthropometry_id"
      +]
  2. First observed

TDQS

C2.6/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 does add genuine behavioral context beyond them: 'Bulk support: accepts patient_ids, anthropometry_ids for batched execution', which tells the agent the tool can fan out over many IDs in one call. It says nothing about pagination defaults or error behavior when an ID does not exist.

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?

The structure is reasonable: capability statement, action list, then bulk note. But the '[Flattened action: get]' artifact and the enumeration of actions that belong to sibling tools are low-value or actively confusing text that an agent must reconcile with the actual schema.

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 no parameter descriptions, the definition leaves too much unresolved: pagination controls, the account parameter, and the meaning of tipo are unexplained. The action-vs-sibling mismatch also risks the agent calling the wrong tool for a list or latest-measurement request.

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 it only partially does: it names patient_id, anthropometry_id, tipo and the two bulk arrays and hints at pagination. It never explains skip/take (defaults 0/50), what 'tipo' values mean, or what 'account' selects, leaving several required-to-call parameters 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 opening sentence names a specific verb and resource with concrete data covered: 'Read anthropometric evaluations in Dietbox (weight, height, BMI, body composition).' However, the description then enumerates list/get/get_latest actions even though this tool is '[Flattened action: get]' and those other actions exist as sibling tools (dietbox_antropometria_list, dietbox_antropometria_get_latest), so the actual scope of this tool is muddied rather than clarified.

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

Usage Guidelines2/5

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

It gives per-action hints ('list requires patient_id', 'get by anthropometry_id'), but those hints largely describe sibling tools rather than this one, where anthropometry_id is the only required parameter. There is no statement of when to prefer this tool over dietbox_antropometria_list or dietbox_antropometria_get_latest, and no exclusion guidance.

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.