Skip to main content
Glama

Move the day of a task an agent filed

reschedule
DestructiveIdempotent

Change the date or deadline of an agent-filed task when new information shifts its timing; set either value to null to remove that date without changing other details.

Instructions

Change the date or deadline of a task an agent filed, when what you learnt moves it. A day the person set is theirs. Null takes a day off; nothing else changes.

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

Input Schema

NameRequiredDescriptionDefault
dateNoThe day it is to be done, or with a deadline the day work starts (2026-08-31); null takes it off
taskYesThe task id
deadlineNoThe day it is owed by; null takes it off

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.43.2
    • changedInput schema / properties / date / description
      Previous value: -"The day it is to be done, or with a deadline the day the work starts (2026-08-31), or null to take it off"New value: +"The day it is to be done, or with a deadline the day work starts (2026-08-31); null takes it off"
    • changedInput schema / properties / deadline / description
      Previous value: -"The day it is owed by, only once it passes is the task overdue, or null to take it off"New value: +"The day it is owed by; null takes it off"
    • changedInput schema / properties / task / description
      Previous value: -"The task's id, as `find` or `propose` gave it"New value: +"The task id"
  2. Changed2 schema fields changedv1.39.1
    • changedInput schema / properties / date / description
      Previous value: -"The day it is to be done (2026-08-31), or null to take it off"New value: +"The day it is to be done, or with a deadline the day the work starts (2026-08-31), or null to take it off"
    • changedInput schema / properties / deadline / description
      Previous value: -"The day it is owed by, or null to take it off"New value: +"The day it is owed by, only once it passes is the task overdue, or null to take it off"
  3. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=true and readOnlyHint=false; the description adds meaningful context with 'nothing else changes', which bounds the mutation to the two date fields. It does not explain why the call is destructive or what a cleared field does to dependents, and 'Null takes a day off' merely restates the schema.

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 free of filler. The phrasing is compressed to the point of being slightly cryptic ('when what you learnt moves it', 'A day the person set is theirs'), costing a beat of parsing.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a three-parameter partial-mutation tool with no output schema and no annotations covering semantics, the definition covers intent and the ownership boundary but says nothing about the response, failure on an unknown task id, or the interaction with the two date fields.

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 coverage is 100%, so the baseline is 3. The description's only parameter claim ('Null takes a day off') duplicates what the schema already says for both `date` and `deadline`, so it adds no meaning beyond the structured field docs.

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 description gives a specific verb-plus-resource: change the `date` or `deadline` of a task an agent filed. The scope qualifier (only agent-filed tasks) is genuinely differentiating, though it never names a sibling such as `move` to route the agent explicitly.

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?

It states when to invoke ('when what you learnt moves it') and an exclusion ('A day the person set is theirs'), which is real when-not guidance. It stops short of naming an alternative tool for the person-set case, so the agent must infer that it should simply not act.

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