Skip to main content
Glama

Omics Health Chile

Calcular dosis de omega-3

calcular_omega3
Read-onlyIdempotent

Estima cuánto EPA + DHA al día se asocia, en promedio, con subir el Índice Omega-3 desde un valor actual a una meta en unas 13 semanas (Walker y cols., 2019).

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": {
      "indice_actual": "<indice_actual>",
      "meta": "<meta>"
    },
    "name": "calcular_omega3"
  }
}

Input Schema

NameRequiredDescriptionDefault
metaYesMayor que el actual, hasta 10.
formaNoForma química según la etiqueta del producto. Si se omite, se asume triglicérido y la respuesta lo dice.
indice_actualYesEntre 2 y 8.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, closed-world and non-destructive behavior, so the description's job is to add context -- and it does: the result is a population-average estimate from a cited study (Walker et al., 2019) over a fixed ~13-week horizon, not a personalized prescription. What it does not state is the unit of the returned amount (e.g., mg/day), which is the main remaining behavioral gap.

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?

A single dense sentence with the quantity being estimated front-loaded, the timeframe and the source trailing. Nothing is redundant, though the embedded clause makes it slightly hard to scan.

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 3-parameter calculator whose schema is fully documented and whose annotations carry the safety profile, the description supplies the method, horizon and provenance needed to interpret the answer. Only the output unit and the linear/average nature of the estimate are unstated, which are minor for a tool with no output schema.

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 100%: each parameter already documents its range and the triglicerido/etil_ester enum, including the default when forma is omitted. The description adds no parameter-level meaning beyond that, so baseline 3 applies.

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?

Names a specific verb (estima) and a precisely scoped output: daily EPA+DHA associated with raising the Omega-3 Index from a current value to a target over ~13 weeks. This is clearly distinct from the sibling tools (product search, testing, form choice, purchasing), though it does not explicitly name them.

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?

The scenario of use is strongly implied -- you have a current index and a goal and want a dose estimate -- but there is no explicit when-to-use/when-not statement, no prerequisites, and no routing to alternatives such as que_test_elegir or que_forma_elegir.

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