Skip to main content
Glama

Omics Health Chile

Qué forma elegir

que_forma_elegir
Read-onlyIdempotent

Devuelve un resumen de las formas de un nutriente (magnesio, hierro, zinc, selenio, B12, folato, vitamina D, vitamina C, omega-3 o creatina) y el enlace a su ficha de referencia en omicshealth.cl.

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": {
      "nutriente": "<nutriente>"
    },
    "name": "que_forma_elegir"
  }
}

Input Schema

NameRequiredDescriptionDefault
nutrienteYesNutriente a consultar: magnesio, hierro, zinc, selenio, B12, folato, vitamina D, vitamina C, omega-3 o creatina.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / nutriente / description
      Added value: +"Nutriente a consultar: magnesio, hierro, zinc, selenio, B12, folato, vitamina D, vitamina C, omega-3 o creatina."
  2. First observed

TDQS

B3.4/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 a closed world, so safety is fully covered for free. The description adds what the caller receives — a summary of forms plus a link to the reference sheet on omicshealth.cl — which is useful, but says nothing about behavior for nutrients outside the list or about output length/format.

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?

One sentence, front-loaded with the verb and the return content, with no filler. The only cost is repeating the full nutrient enumeration that the schema already contains, which makes the sentence longer than strictly necessary.

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

Completeness3/5

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

For a single-parameter, read-only lookup with no output schema, a fairly complete picture could be given, and the description does name the return content. However it omits error behavior for unsupported values and any hint of the summary's structure, leaving modest gaps.

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% and the single parameter's schema description already enumerates exactly the same nutrient values, so the description merely duplicates it. Baseline 3 is correct when the schema carries all parameter meaning.

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?

States a specific verb and resource ("Devuelve un resumen de las formas de un nutriente") and bounds the scope with an explicit nutrient list. It does not reference the similarly shaped sibling que_test_elegir, so the contrast must be inferred from the nutrient-vs-test wording.

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 enumerated nutrient list implies when the tool applies, but there is no statement of when not to use it, no mention of alternatives such as que_test_elegir or buscar_productos, and no prerequisites. Usage must be inferred from the domain vocabulary rather than read from the text.

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