Skip to main content
Glama

Omics Health Chile

Buscar productos

buscar_productos
Read-onlyIdempotent

Busca productos en el catálogo público de omicshealth.cl (Chile) por palabra clave y, opcionalmente, por marca. Devuelve hasta 8 resultados con nombre, marca, precio en CLP, disponibilidad y enlace.

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": "buscar_productos"
  }
}

Input Schema

NameRequiredDescriptionDefault
marcaNoOpcional. Marca, por ejemplo 'Momentous'.
consultaYesQué se busca, por ejemplo 'magnesio glicinato' o 'test microbioma'.

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 cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description's job is narrower. It still adds real value by disclosing the result cap ('hasta 8 resultados') and the exact fields returned including pricing currency (CLP) and a link — details an agent could not derive from the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with the action and scope, followed by the return shape. Every clause carries information: catalog, country, query mode, optional filter, result limit, and returned fields.

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 simple two-parameter read tool with no output schema, the description covers both input semantics and the return payload, which is what an agent needs. Minor gaps remain around whether results are ranked or truncated arbitrarily and whether the catalog is Spanish-only, but nothing essential for correct invocation is missing.

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 coverage is 100% and both parameters already carry examples ('magnesio glicinato', 'Momentous'). The description restates the optionality of the brand filter but adds no syntax, matching, or accent-handling guidance beyond what the schema provides, so the baseline holds.

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 resource ('Busca productos en el catálogo público de omicshealth.cl') and scopes the search to keyword plus optional brand. It is clear what the tool does, but it never names or contrasts with the related sibling 'donde_comprar', so an agent must infer the split between product search and purchase-location 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: the phrase 'por palabra clave y, opcionalmente, por marca' suggests when the tool fits, and 'catálogo público' hints at a non-authenticated retail context. There is no explicit when-to-use, when-not-to-use, or alternative tool named.

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