Skip to main content
Glama

Omics Health Chile

Qué test elegir

que_test_elegir
Read-onlyIdempotent

Devuelve un resumen de la tecnología de test que corresponde a un tema (microbioma, epigenética y edad biológica, omega-3 o función mitocondrial) y el enlace a su página 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": {
      "tema": "<tema>"
    },
    "name": "que_test_elegir"
  }
}

Input Schema

NameRequiredDescriptionDefault
temaYesTema del test: microbioma, epigenética, edad biológica, omega-3 o función mitocondrial.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / tema / description
      Added value: +"Tema del test: microbioma, epigenética, edad biológica, omega-3 o función mitocondrial."
  2. First observed

TDQS

A3.5/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 fully covered and the description need only add return behavior. It does add that the output is a summary plus a reference URL, which is useful. What is missing is behavior for an unrecognized 'tema' value: the parameter is a free string with no enum, and the description never says whether an unknown topic errors or returns nothing.

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 with the returned value first and the enumeration second; nothing is padding. The only minor waste is re-listing the topics that the schema already enumerates.

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 one-parameter read-only lookup with no output schema, the description covers what is returned (a summary and a link), which is the essential shape of the response. It is not fully complete because invalid-topic behavior is unspecified and the topic list is phrased slightly differently from the 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% and there is only one parameter, so the baseline is 3. The description restates the same topic list as the schema rather than adding meaning — it does not clarify accepted spellings, accents, partial matches, or how 'epigenética y edad biológica' maps onto the two separately listed values in the schema.

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 and result ('Devuelve un resumen de la tecnología de test') and anchors it to four named domains, plus a reference link on omicshealth.cl. That makes the resource concrete enough to separate it from a product search or a definition lookup. It stops short of naming a sibling, so 4 rather than 5.

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: an agent can infer this is the tool for 'which test applies to topic X', but there is no explicit when-to-use statement, no exclusion, and no pointer to alternatives such as que_forma_elegir or buscar_productos. Adequate but noticeably thin for a topic-routing tool.

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