Skip to main content
Glama

set_task_deadline

Idempotent

Set or clear a task deadline using Gregorian, Jalali, or ISO dates, with Tehran time handling for accurate scheduling.

Instructions

Set or clear (deadline=None) a task's deadline.

Accepts "2026-11-20 14:30" (Gregorian, Tehran time), "1405/08/30 14:30" (Jalali) or ISO with Z. A date without time means 23:59 Tehran.

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>",
      "deadline": "<deadline>"
    },
    "name": "set_task_deadline"
  }
}

Input Schema

NameRequiredDescriptionDefault
task_idYes
deadlineYes

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 cover the safety profile (non-destructive, idempotent, mutating), so the description's job is to add operational context — and it does, disclosing accepted input formats, the Tehran-time basis, Jalali/Gregorian/ISO handling, and the 23:59 default for a bare date. It stops short of saying whether a deadline change triggers reminders or notifications, which is the main behavioral unknown left.

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?

Three short sentences, front-loaded with the action, then the format contract. Every clause supplies information an agent would otherwise have to guess; nothing is redundant with the schema or annotations.

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?

An output schema exists, so return values need not be explained, and the description fills the genuinely risky gaps: date format ambiguity and timezone. What remains unsaid is whether past dates are rejected and whether reminders are affected — relevant for an openWorldHint tool but not blocking correct invocation.

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 0%, so the description carries the full burden for `deadline`, and it delivers: exact accepted formats, timezone, and the null-to-clear convention. `task_id` gets no explanation, but its meaning is unambiguous from the name and required status.

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 opening sentence states a specific verb and resource ('Set or clear ... a task's deadline') and even encodes the clearing mechanism inline. It is immediately distinguishable from unrelated siblings like complete_task or add_task_comment, though it does not explicitly contrast with its nearest sibling set_task_reminder.

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 rather than stated: an agent can infer this is the tool for assigning or removing a due date. There is no explicit guidance on when to prefer this over set_task_reminder or update_task, and no exclusions or prerequisites are mentioned.

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