Skip to main content
Glama

Omics Health Chile

Definir un término

definir_termino
Read-onlyIdempotent

Define en español un término de los tests de microbioma, epigenética u omega-3 (ómica, metagenómica shotgun, metatranscriptómica, metilación del ADN, reloj epigenético, DunedinPACE, OMICmAge, SYMPHONYAge, Índice Omega-3, CST) y enlaza la ficha con su fuente.

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": {
      "termino": "<termino>"
    },
    "name": "definir_termino"
  }
}

Input Schema

NameRequiredDescriptionDefault
terminoYesTérmino a definir, por ejemplo 'DunedinPACE' o 'metagenómica shotgun'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / termino / description
      Added value: +"Término a definir, por ejemplo 'DunedinPACE' o 'metagenómica shotgun'."
  2. First observed

TDQS

A3.7/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. The description adds that output is Spanish-language and tied to a source, but the phrase "enlaza la ficha con su fuente" is ambiguous — it could be read as persistence/link-creation (which would conflict with readOnly) or simply that the returned entry cites its source; this ambiguity is the definition's main 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?

One sentence, front-loaded with the action verb and output language, with no filler. The eleven-item parenthetical list is long and slightly cumbersome, though it does earn its place by scoping valid inputs.

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 single-parameter, read-only lookup with no output schema, the definition covers what the tool does, which terms it accepts, and that the result includes a source. It would be complete at a 5 if it clarified the return shape (definition length, source format) or behaviour for unknown terms, since no output schema exists to carry that.

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 the single parameter already carries examples (DunedinPACE, metagenómica shotgun), so the baseline applies. The description's enumeration of supported term families adds modest value by signalling the accepted vocabulary, but it does not clarify matching behavior (case sensitivity, partial terms, or what happens for a term outside the list).

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description leads with a specific verb and resource ("Define en español un término") and scopes it to named domains — microbiome, epigenetics, omega-3 — with eleven concrete glossary examples (DunedinPACE, metagenómica shotgun, Índice Omega-3, CST…). An agent can immediately tell this apart from siblings such as buscar_productos, calcular_omega3, and que_test_elegir, which handle products, calculations, and test selection rather than definitions.

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 the domain scope: it is clear the tool is for looking up glossary terms, but the description never states when to prefer it over a sibling (e.g. que_test_elegir for choosing an assay vs. this for explaining a term) or what to do with an out-of-scope term. No when-not-to-use or prerequisite guidance is given.

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