Skip to main content
Glama

Update several tasks

update_tasks
Idempotent

Change up to 50 tasks in one call (each entry like update_task: title, dayKey, timeMinutes, reminder). Use it to reschedule or rename several tasks at once, e.g. move a list of tasks to another day. If the user did not clearly ask for all of these changes, confirm first. One undo_last_change reverts the whole call.

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": {
      "updates": "<updates>"
    },
    "name": "update_tasks"
  }
}

Input Schema

NameRequiredDescriptionDefault
updatesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare this is a non-read-only, non-destructive, idempotent, closed-world mutation. The description adds valuable batch-specific context: confirm ambiguous bulk changes, and one undo_last_change reverts the whole call. It does not disclose partial-failure or atomicity behavior.

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?

The definition is four short sentences with the batch scope front-loaded. The usage example, confirmation safeguard, and undo note each earn their place, with no filler.

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?

Given a batch mutation tool with annotations and no output schema, the description covers intended use, batch limit, confirmation, and undo scope. It is nearly complete, though it could state what happens if some updates fail.

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?

The nested schema itself documents each field in detail, including id sources, null semantics for dayKey/timeMinutes/reminders, numeric ranges, and the 50-item cap. The description only summarizes a few fields and largely repeats the update_task entry shape, adding little beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ('Change'), resource ('tasks'), and batch scope ('up to 50 tasks in one call'). The reference to 'update_task' clarifies the per-entry shape and distinguishes this batch operation from the single-task sibling.

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?

Explicitly says to use it for rescheduling or renaming several tasks at once and gives a concrete example ('move a list of tasks to another day'). It also adds a confirmation requirement when the user did not clearly request all changes, though it does not explicitly name when to prefer update_task or move_tasks.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources