Skip to main content
Glama

Pedir una reunión

pedir_reunion
Read-onlyIdempotent

Entrega los enlaces para que la persona pida su consulta con MisCausas.cl: la agenda del sitio y un WhatsApp con el mensaje escrito. No reserva ni guarda datos; la persona envía el mensaje o elige la hora, y el estudio confirma la reunión con ella.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "pedir_reunion"
  }
}

Input Schema

NameRequiredDescriptionDefault
horaNoUna hora tal como la entrega horas_disponibles («jueves 20 a las 16:00»).
procedimientoNoLa vía que dio evaluar_situacion, para que el mensaje la mencione.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

The annotations already declare readOnly, idempotent, non-destructive and closed-world, and the description correctly reinforces this by stating it does not book or save data. It goes further with a genuine behavioral fact the annotations cannot convey: the human must send the WhatsApp message or pick the slot, and the firm confirms afterwards. It adds no detail on link expiry or repeated-call behavior, so 4 rather than 5.

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 tight sentences. The deliverable is front-loaded, followed immediately by the non-effect disclaimer and the human-confirmation loop. No filler and nothing repeated from the annotations.

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?

For a simple, side-effect-free, two-optional-parameter tool with no output schema, the description supplies what an agent needs: what comes back (calendar link plus WhatsApp link with a written message) and what the tool deliberately does not do. Nothing essential 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 are already documented well in the schema, including cross-references to horas_disponibles and evaluar_situacion. The description adds nothing about 'hora' or 'procedimiento' beyond what the schema states, so the baseline of 3 applies.

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 opens with a concrete verb and result — 'Entrega los enlaces' — and specifies exactly what the links are: the site calendar and a pre-written WhatsApp message. It also draws the boundary that it does not reserve or store anything, which separates it cleanly from horas_disponibles and evaluar_situacion.

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?

The usage context is clear: this is the hand-off step where the person actually books, after a procedure has been chosen and a time retrieved. However, it never explicitly names the sibling tools it should follow (horas_disponibles, evaluar_situacion) or states when not to call it, leaving that routing to inference from the schema.

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