PilotControl

Agendar un recordatorio de un chat de WhatsApp

whatsapp_add_reminder

Idempotent

Agenda un recordatorio (REMINDER) o un evento (EVENT) con una nota para un chat de WhatsApp (conversation_ref). Queda en la agenda de PilotControl y no envía nada al contacto.

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": {
      "operation_id": "<operation_id>",
      "conversation_ref": "<conversation_ref>",
      "scheduled_for": "<scheduled_for>"
    },
    "name": "whatsapp_add_reminder"
  }
}

Input Schema

Name	Required	Description	Default
`kind`	No		REMINDER
`note`	No
`operation_id`	Yes	Repetirlo no agenda dos veces
`scheduled_for`	Yes
`conversation_ref`	Yes	conversation_ref de list_conversations (un chat de WhatsApp)

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 7, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare non-destructive, idempotent and closed-world, and the description adds genuinely new context: the entry lands in the PilotControl agenda and nothing is delivered to the contact. It does not discuss what a repeat call returns (only the schema's operation_id note covers dedup), so it stops short of full behavioral detail.

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: the first establishes what is created and for which chat, the second establishes where it lives and that no message is sent. No filler, and the most important behavioral fact is front-loaded.

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 closed-world, non-destructive creation tool with no output schema, the description covers purpose, side effects and ref sourcing adequately. It could go one step further and mention the sibling update tool for later modification, or what the agent gets back on success.

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 only 40%, so the description must carry weight: it glosses 'kind' as a reminder-versus-event choice, 'note' as the accompanying note, and anchors conversation_ref to a WhatsApp chat. Only scheduled_for receives no explanation beyond its date-time format, which is the one remaining gap for a 5-parameter tool.

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?

States a specific verb (agenda) plus the two creatable artifacts (REMINDER recordatorio / EVENT evento) tied to a WhatsApp chat via conversation_ref. It clearly separates itself from messaging siblings by declaring it sends nothing to the contact, though it never names the sibling (whatsapp_schedule_message / whatsapp_send_message) it is contrasted with.

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?

The clause 'no envía nada al contacto' functions as a when-not signal, implicitly steering the agent away from send/schedule-message tools for messaging. However, there is no explicit statement of when to choose this over whatsapp_schedule_message or whatsapp_update_reminder, and no prerequisites are given.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All PilotControl tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?