Skip to main content
Glama

set_task_reminder

Idempotent

Schedule or clear a task reminder date so Mizito files the task under today, overdue, or upcoming and notifies assignees at the right time.

Instructions

Schedule a task ("زمان یادآوری"), or clear it with when=None. This is the date Mizito uses to put a task under today / overdue / upcoming, and when it reminds the assignees. Same date formats as create_task. (The web app calls this "snooze".)

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_id": "<task_id>",
      "when": "<when>"
    },
    "name": "set_task_reminder"
  }
}

Input Schema

NameRequiredDescriptionDefault
whenYes
task_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare non-read-only, idempotent, non-destructive, open-world, so the description doesn't need to cover safety. It adds real behavior beyond them: that None clears an existing reminder and that the date controls bucket placement and assignee notifications. It doesn't say whether the caller must be the assignee/creator or what happens with past dates.

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 its inverse, then supporting semantics; no filler sentences. The Persian gloss and the 'snooze' alias each earn their place by aiding intent matching. Slight looseness in the parenthetical asides but nothing to cut.

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 mutation with full annotations and an output schema, the description covers the action, the clearing case, and the side effects on ordering and notifications. The remaining omission is caller permissions/eligibility, which is a minor gap against an otherwise complete definition.

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 description coverage is 0%, so the description carries the burden. It explains `when` (a date, or None to clear) but defers the actual accepted formats to create_task rather than stating them, forcing a cross-tool lookup. `task_id` is never mentioned, though its meaning is self-evident from the tool name.

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 and resource ('Schedule a task reminder'), plus the inverse operation ('clear it with when=None'). It also explains the semantic role of the date (bucketing into today/overdue/upcoming and driving assignee notifications), which lets an agent distinguish it from a plain field update. It stops short of naming set_task_deadline as the sibling to avoid, so the deadline-vs-reminder boundary must be inferred from the tool names.

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?

Gives clear context for both directions of use: set a reminder when you want the task surfaced/notified, or pass when=None to remove it. The note that the web app labels this 'snooze' is a valuable alias mapping for interpreting user requests. No explicit exclusion against set_task_deadline or update_task, which is the main gap.

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