Skip to main content
Glama

FetologIA — calculadoras de medicina fetal

Doppler das artérias oftálmicas maternas (z-score e percentil)

calcular_doppler_oftalmicas
Read-onlyIdempotent

Doppler das artérias oftálmicas maternas (z-score e percentil). Escore Z, percentil e classificação dos 6 índices do Doppler da artéria oftálmica materna (IR, IP, PVS, P2, razão de picos e VDF), 20 a 41 semanas; vários índices por chamada. Faixa de validade: 20+0 a 41+0 semanas (em 41 semanas, apenas 41+0). Valores devem ser a média das duas artérias oftálmicas. Referências: Diniz ALD et al. J Ultrasound Med 2026;45:819-831 — curvas de referência do Doppler da artéria oftálmica em gestações de baixo risco. DeVore GR. J Ultrasound Med 2026 — método do escore Z com semi-desvios assimétricos (calculadora do Supplement 1). Página para o médico conferir: https://fetologia.com/calculadoras/avancadas/doppler-oftalmicas Material de estudo (origem do método, técnica de medida, interpretação): https://fetologia.com/calculadoras/avancadas/doppler-oftalmicas/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": {
      "ig_semanas": "<ig_semanas>"
    },
    "name": "calcular_doppler_oftalmicas"
  }
}

Input Schema

NameRequiredDescriptionDefault
piNoÍndice de Pulsatilidade (média das 2 artérias).
riNoÍndice de Resistência (média das 2 artérias).
pvrNoRazão de Picos de Velocidade (P2/PSV). Se ausente e PSV+P2 fornecidos, é calculada automaticamente.
ig_diasNoDias (0-6). Default 0. Em 41 sem, apenas 41+0 é aceito.
p2_cm_sNoSegundo Pico Sistólico em cm/s.
edv_cm_sNoVelocidade Diastólica Final em cm/s.
psv_cm_sNoPico de Velocidade Sistólica em cm/s.
ig_semanasYesSemanas de IG (20 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 declare readOnly, idempotent, non-destructive, closed-world behavior, so safety is covered. The description adds real behavioral context beyond that: the accepted gestational-age window including the 41+0 edge case, the input precondition that each index be averaged over both arteries, and named reference sources for the curves and Z-score method, which lets the agent judge the basis of the computation.

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?

Content is front-loaded: what is computed, then validity range, then provenance. The opening sentence largely restates the title, and the full bibliographic citations plus two URLs add length, but they serve verifiability and method provenance, so the cost is mostly justified.

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 calculation tool with no output schema, the description is adequate: it names the computed outputs (Z-score, percentile, classification), the index set, the valid gestational window and the source curves. It stops short of describing what happens for out-of-range values or how the classification bands are derived, which would close the remaining gap.

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 baseline is 3, but the description adds meaning beyond the schema: it enumerates the six clinical indices that the parameters represent as a set and clarifies that several indices may be supplied in a single call. It also restates the 41+0 acceptance rule, reinforcing the ig_dias/ig_semanas constraint in semantic terms.

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 states a specific verb+resource: it computes Z-score, percentile and classification for the six ophthalmic-artery Doppler indices (IR, IP, PVS, P2, peak ratio, VDF) between 20 and 41 weeks. The named index set makes it clearly distinguishable from the plainer sibling 'calcular_doppler', though no sibling is explicitly named as an alternative.

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 gives operative constraints on use — validity window 20+0 to 41+0 (only 41+0 accepted at 41 weeks) and the requirement that values be the mean of both ophthalmic arteries — which effectively tells the agent when the tool is applicable. However, there is no explicit statement of when to prefer this over sibstools like calcular_doppler, nor of what to do when the gestational age falls outside the range.

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