Skip to main content
Glama

Set a task to ring

remind
Idempotent

Adds reminder times to a task so it rings at given days and hours. Use it for one-off alerts; recurring routines schedule themselves.

Instructions

Make a task ring at given moments. It adds to what the task rings at and never removes a reminder (read shows them). Not for what repeats: a routine comes back on its own.

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": {
      "task": "<task>",
      "at": "<at>"
    },
    "name": "remind"
  }
}

Input Schema

NameRequiredDescriptionDefault
atYesEach a day and an hour, like 2026-08-30T20:00
taskYesThe task id

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.43.2
    • changedInput schema / properties / at / description
      Previous value: -"When to ring, each as a day and an hour like 2026-08-30T20:00"New value: +"Each a day and an hour, like 2026-08-30T20:00"
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

The description adds real behavioral context beyond the annotations: the operation is purely additive and never removes existing reminders, which is the key semantic distinction the annotations do not convey. It does not mention permissions or failure behavior, but for a low-risk, non-destructive additive tool this is a solid disclosure.

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?

Three short sentences, front-loaded with the action and followed by the additive guarantee and the exclusion. The clause 'Not for what repeats: a routine comes back on its own' is slightly cryptic in its vocabulary but earns its place.

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 two-parameter tool with no output schema, the description covers action, additive semantics, and the inspection alternative. It does not state what a successful call returns, but pointing to `read` for viewing largely closes that gap.

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?

Schemas cover 100% of both parameters, including the timestamp format example, so the description adds little beyond noting that multiple moments are supplied. Baseline 3 applies when the schema does the heavy lifting.

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?

The first sentence states a specific verb and resource: make a task ring at given moments. It is clearly distinct from the read-only sibling it names (`read` shows reminders), though the phrase 'at given moments' is slightly vaguer than 'add reminders to a task'.

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

Usage Guidelines5/5

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

It gives an explicit exclusion ('Not for what repeats: a routine comes back on its own') and routes inspection of existing reminders to `read`. An agent knows both when to call this and when to call something else.

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