Skip to main content
Glama

FetologIA — calculadoras de medicina fetal

Percentil e escore Z de biometria fetal e peso estimado (INTERGROWTH-21st)

calcular_intergrowth
Read-onlyIdempotent

Percentil e escore Z de biometria fetal e peso estimado (INTERGROWTH-21st). Percentil e escore Z de CA, DBP, CF, CC, DOF e peso fetal estimado pelas curvas INTERGROWTH-21st, com classificação clínica. Faixa de validade: Biometria: 14 a 41 semanas (medidas em mm). Peso fetal estimado: INTERGROWTH-21st de 22 a 40 semanas; Hadlock 1991 em 14–21 e 41 semanas (em gramas). A resposta informa em "referencia_usada" qual tabela foi aplicada. Referências: Papageorghiou AT et al. (INTERGROWTH-21st). Lancet 2014 — padrões internacionais de biometria fetal (CA, DBP, CF, CC, DOF). Stirnemann J et al. (INTERGROWTH-21st). Ultrasound Obstet Gynecol 2020 — peso fetal estimado, 22 a 40 semanas. Hadlock FP et al. Radiology 1991 — peso fetal estimado fora da faixa INTERGROWTH (14–21 e 41 semanas). Página para o médico conferir: https://fetologia.com/calculadoras/percentil-fetal Material de estudo (origem do método, técnica de medida, interpretação): https://fetologia.com/calculadoras/percentil-fetal/entenda

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": {
      "parametro": "<parametro>",
      "idade_gestacional_semanas": "<idade_gestacional_semanas>",
      "valor_medido": "<valor_medido>"
    },
    "name": "calcular_intergrowth"
  }
}

Input Schema

NameRequiredDescriptionDefault
parametroYesParâmetro biométrico (siglas em inglês): AC=circunferência abdominal (CA); BPD=diâmetro biparietal (DBP); FL=comprimento do fêmur (CF); HC=circunferência cefálica (CC); OFD=diâmetro occipitofrontal (DOF); EFW=peso fetal estimado.
valor_medidoYesMedida em mm para parâmetros biométricos (AC, BPD, FL, HC, OFD), ou em gramas para EFW. Não aceita valores negativos nem zero.
idade_gestacional_diasNoDias adicionais (0-6). Default 0 quando não informado.
idade_gestacional_semanasYesSemanas completas de idade gestacional (componente inteiro de 14 a 41).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover the safe-read profile (readOnly, idempotent, non-destructive, closed-world), so the description's job is extra context — and it delivers: unit conventions (mm vs grams), per-parameter validity ranges, an automatic fallback to Hadlock 1991 outside the INTERGROWTH window, and the fact that the response exposes a 'referencia_usada' field so the agent can report which table was applied. It stops short of describing the full response shape or precision/rounding of the returned percentile and Z-score.

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 purpose is front-loaded in the first sentence and the operational constraints (ranges, units, fallback) follow in a logical order. There is some redundancy — the opening repeats the title verbatim and states 'Percentil e escore Z' twice — and the full bibliographic citations plus two URLs add length that is defensible for a clinical tool but not strictly needed for correct invocation.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only calculator with no output schema, the description supplies what an agent needs: inputs and their units, valid gestational windows, the internal reference-selection rule, and the existence of a clinical classification and 'referencia_usada' in the response. The remaining gap is that the exact response fields (percentile value, Z-score, classification labels) are named only in passing rather than enumerated.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3; the description earns above that by adding meaning the schema cannot express — the 22–40 week restriction applies only to EFW while 14–41 applies to biometry, which is a real constraint beyond the schema's uniform 14–41 bounds on weeks. The metric/gram unit split and the enum expansion are largely restatements of schema text.

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 names a specific operation and resource — percentile and Z-score for fetal biometry (CA, DBP, CF, CC, DOF) and estimated fetal weight using INTERGROWTH-21st curves, with clinical classification — and enumerates the exact parameters covered. It never distinguishes itself from the similarly named sibling calcular_percentil_fetal, so an agent cannot tell from the text alone which of the two to pick.

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 context is present but implicit: it states the validity window (14–41 weeks for biometry; 22–40 weeks for EFW) and explains that outside that window the tool internally switches to Hadlock 1991, which tells the agent when inputs are acceptable. It gives no explicit when-to-use / when-not-to-use instruction against alternatives such as calcular_percentil_fetal, so routing must be inferred.

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.

Resources