Skip to main content
Glama

Hablar con el agente de VITALINK

talk_to_vitalink

Envía el mensaje del paciente al agente de salud de VITALINK (México) y devuelve su respuesta en reply, para mostrarla al paciente. El agente explica el servicio de cotizaciones de cirugía y conversa sobre el procedimiento que el paciente quiere cotizar, su zona y sus fechas; no diagnostica ni da precios. VITALINK guarda la conversación para trazabilidad y calidad; conversation se envía de vuelta en la siguiente llamada. Si lo que pide el paciente necesita su cuenta, devuelve needsAccount: true.

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": {
      "message": "<message>"
    },
    "name": "talk_to_vitalink"
  }
}

Input Schema

NameRequiredDescriptionDefault
messageYesEl mensaje del paciente para el agente de VITALINK sobre lo que quiere cotizar o consultar (procedimiento, zona, fechas, dudas). No incluyas su nombre completo, teléfono, correo, dirección ni números de identificación: VITALINK no los necesita aquí.
conversationNoToken opaco de la respuesta anterior (conversation), sin cambiarlo; omítelo al empezar. No contiene nada que la app deba leer.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only declare the safety/mutation profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false). The description adds substantive behavior the agent could not infer: the agent's competence boundaries (no diagnosis, no prices), a privacy/traceability disclosure that VITALINK stores the conversation, the round-trip convention for the conversation token, and the needsAccount signal. This is well beyond structured data.

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?

Front-loaded with the action and destination, then scope limits, then storage/token behavior, then the escalation signal. Dense but every sentence carries distinct information; no filler.

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

Completeness5/5

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

No output schema exists, yet the description names the returned fields (reply, needsAccount, conversation) and how to reuse them, so the agent knows exactly what to expect and do next. For a two-parameter, single-purpose conversational tool this is complete.

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. The description nevertheless adds value by explaining the stateful loop — the previous response's conversation must be sent back on the next call — and that reply/needsAccount are the fields to surface to the patient, meaning the schema alone would not reveal the call sequence.

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?

States a specific verb and resource ('Envía el mensaje del paciente al agente de salud de VITALINK') plus the scope of what that agent does (explains surgery-quote service, discusses procedure/zone/dates) and explicitly what it does not do ('no diagnostica ni da precios'). The closing sentence about needsAccount distinguishes it from the sibling account variant without needing the sibling's schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Clear context for use: send patient questions about procedures, zone and dates to the agent. It also signals an escalation path ('Si lo que pide el paciente necesita su cuenta, devuelve needsAccount: true'), which implies when to move to the account-based sibling, though it never names that sibling explicitly.

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