Sergio by Serviche

Set a reminder on a conversation

set_conversation_reminder

Idempotent

Adds a reminder on a conversation, as the thread's bell does: remind_at (ISO 8601) and an optional note become a task due then. hide_until_due: true also tucks the thread away until the reminder is due (a reply from the person brings it back). Pass the same idempotency_key when retrying; a repeat returns the first reminder.

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": {
      "conversation_id": "<conversation_id>",
      "remind_at": "<remind_at>",
      "idempotency_key": "<idempotency_key>"
    },
    "name": "set_conversation_reminder"
  }
}

Input Schema

Name	Required	Description
`note`	No
`remind_at`	Yes
`hide_until_due`	No
`conversation_id`	Yes
`idempotency_key`	Yes	Your id for this operation (8-128 of A-Z a-z 0-9 . _ : -). Reuse it on every retry of the same operation; use a new one for a new operation.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 8, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Beyond the annotations (non-read-only, idempotent, non-destructive), the description discloses the real side effect: a task is created with remind_at as its due time, and hide_until_due hides the thread until a reply restores it. It also explains the idempotency contract concretely ('a repeat returns the first reminder'), which goes past idempotentHint=true. Auth/permission requirements are the notable omission.

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?

A single tight paragraph that front-loads the core action, then the optional hiding behavior, then the retry rule. No sentence is filler, and the ordering matches how an agent would reason about calling it.

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 five-parameter mutation with no output schema, the description covers the essential unknowns: side effects, the hide-until-due lifecycle, and idempotent retry semantics. Only permission requirements and the shape of the returned reminder are unaddressed, which are minor gaps here.

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 description coverage is only 20% (only idempotency_key documented inline), so the description must compensate, and it does: it defines remind_at's format and effect, the role of note as the task content, and the exact behavior of hide_until_due. conversation_id is left as self-evident via its uuid format.

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?

Specific verb and resource ('Adds a reminder on a conversation') are stated immediately, and the anchor 'as the thread's bell does' clarifies the mechanism. It does not name the nearest sibling (snooze_conversation, dismiss_conversation_reminders), so the boundary between this and similar reminder/snooze tools is left to the agent.

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 implied through the hide_until_due scenario ('tucks the thread away until the reminder is due') and the retry rule, which helps the agent decide when to set this option. However, there is no explicit when-not guidance and no routing to snooze_conversation or dismiss_conversation_reminders, which are close alternatives in the sibling list.

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

All Sergio by Serviche 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?