Skip to main content
Glama

FetologIA — calculadoras de medicina fetal

Doppler obstétrico (artéria umbilical, ACM, CPR, ducto venoso e uterinas)

calcular_doppler
Read-onlyIdempotent

Doppler obstétrico (artéria umbilical, ACM, CPR, ducto venoso e uterinas). Percentil por idade gestacional e interpretação clínica curta do IP/PIV de um vaso do Doppler obstétrico, com sinais de alarme (diástole zero/reversa, onda "a" ausente/reversa). Faixa de validade: Artéria umbilical, ACM e CPR: 20 a 41 semanas. Ducto venoso: 11 a 14 semanas (Maiz) e 21 a 39 semanas (Kessler). Artérias uterinas: 11 a 41 semanas (IP médio das duas artérias). Fora da faixa, a resposta traz "alerta_faixa" e não classifica o valor. Referências: Ciobanu A et al. (Fetal Medicine Foundation). Ultrasound Obstet Gynecol 2019 — IP umbilical, IP da ACM e CPR (n=72.387). Kessler J et al. Ultrasound Obstet Gynecol 2006 — PIV do ducto venoso, 2º/3º trimestre (longitudinal). Maiz N et al. Ultrasound Obstet Gynecol 2008 — PIV do ducto venoso, 11 a 13+6 semanas (faixa 0,73–1,22). Gómez O et al. Ultrasound Obstet Gynecol 2008 — IP médio das artérias uterinas, 11 a 41 semanas. Página para o médico conferir: https://fetologia.com/calculadoras/avancadas/doppler Material de estudo (origem do método, técnica de medida, interpretação): https://fetologia.com/calculadoras/avancadas/doppler/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": {
      "vaso": "<vaso>",
      "ig_semanas": "<ig_semanas>"
    },
    "name": "calcular_doppler"
  }
}

Input Schema

NameRequiredDescriptionDefault
vasoYesQual vaso analisar.
onda_aNoPara vaso=ducto_venoso: status da onda "a". "ausente" e "reversa" indicam descompensação cardíaca fetal.
ig_diasNoDias (0-6). Default 0.
ip_medidoNoPara vaso=umbilical (IP-AU), acm (IP-ACM), uterinas (IP médio das duas) ou cpr (CPR observada).
ig_semanasYesSemanas de IG.
piv_medidoNoPara vaso=ducto_venoso: PIV (Pulsatility Index for Veins).
diastole_zeroNoPara vaso=umbilical: marcar true se diástole zero. Sobrepõe percentil — gravidade máxima.
diastole_reversaNoPara vaso=umbilical: marcar true se diástole reversa. Sobrepõe percentil — urgência clínica.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/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 adds genuine behavioral context beyond that: out-of-range input yields an "alerta_faixa" instead of a classification, and the output includes alarm signs (absent/reversed a-wave, zero/reversed diastolic flow) and a short clinical interpretation.

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 functional content (method, validity bands, out-of-range behavior) is front-loaded and well organized, but roughly half the text is bibliographic citations and two URLs, which are credibility aids rather than invocation guidance. Useful for a clinical tool yet not maximally economical.

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 an 8-parameter, single-purpose calculator with no output schema, the definition covers the validated method, per-vessel gestational ranges, and edge-case behavior, which is what an agent needs to call it correctly. It could still be slightly clearer about the shape of the returned percentile/interpretation fields.

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 100% schema description coverage, the schema already explains each parameter, including vessel-specific fields, enum meanings and the 0–6 day range. The description adds the gestational-age validity bands that constrain ig_semanas per vessel, but otherwise mostly restates the schema baseline rather than adding parameter-level meaning.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb+resource (percentile and short clinical interpretation of PI/PIV for one obstetric Doppler vessel) and enumerates the supported vessels: umbilical artery, ACM, CPR, ductus venosus and uterine arteries. An agent can distinguish this from siblings such as calcular_doppler_oftalmicas or calcular_percentil_fetal without opening the schema.

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?

It gives explicit applicability windows per vessel (umbilical/ACM/CPR 20–41 weeks, ductus venosus 11–14 and 21–39 weeks, uterine 11–41 weeks) and states the fallback behavior outside those ranges ("alerta_faixa", no classification). It does not name a sibling alternative or exclusion, so it stops short of a 5.

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