Skip to main content
Glama

Omics Health Chile

Omics Vital: programas y glosario clínico

omics_vital
Read-onlyIdempotent

Devuelve los programas de membresía publicados en omicsvital.cl con sus precios, o la definición de un término de su glosario (nutriepigenómica, nutrimetagenómica, nutrimetatranscriptómica, medición longitudinal, línea base personal, valor de referencia del cambio, edad biológica, gemelo digital).

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": {
      "consulta": "<consulta>"
    },
    "name": "omics_vital"
  }
}

Input Schema

NameRequiredDescriptionDefault
consultaYesPor ejemplo 'programas', 'precio' o un término como 'nutriepigenómica'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered and the description is consistent with it (content comes from a fixed site). The description adds that only *published* programs are returned, which is useful. It does not say what happens on an unrecognized or ambiguous 'consulta', nor the response shape.

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 front-loaded sentence led by the verb, with the two return modes ordered clearly. The parenthetical term list is long but carries real information rather than filler.

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?

With no output schema, the description must at least characterize return values, and it does: programs with prices, or a term definition. For a one-parameter lookup tool this is close to sufficient; only the unmatched-input behavior is left unspecified.

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, but the description earns more by explaining the two-mode dispatch driven by the single 'consulta' argument and by enumerating the valid glossary terms — a genuine expansion beyond the schema's short example list.

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 verb ('Devuelve') and two concrete resources: membership programs published on omicsvital.cl with their prices, or the definition of a glossary term. It enumerates the glossary terms, so an agent knows the coverage precisely. It does not, however, distinguish this tool from the sibling 'definir_termino', which plausibly handles the same glossary lookup.

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 is only implied through examples: pass 'programas' or 'precio' for programs, or a term name for the glossary. There is no explicit statement of when to prefer this over 'definir_termino' or 'buscar_productos', and no exclusions or failure guidance when 'consulta' matches neither mode.

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