Skip to main content
Glama

Add tasks

add_tasks

Add one or more one-off tasks (up to 50) in a single call. When planning a week or several days, put ALL tasks in one call. Keep titles short, like a to-do list item. Only set a time or reminder when the user gave one or clearly wants it. For something that repeats every day or week use add_repeating_task instead. The tasks appear on the user's phone right away. Can be reverted with undo_last_change.

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": {
      "tasks": "<tasks>"
    },
    "name": "add_tasks"
  }
}

Input Schema

NameRequiredDescriptionDefault
tasksYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare it as a non-read-only, non-destructive, non-idempotent write. The description adds real context beyond that: tasks are visible on the user's phone immediately, and the whole batch can be reverted with undo_last_change. It does not mention duplicate-creation behavior on repeat calls, which matters given idempotentHint=false.

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?

Every sentence carries actionable information — batching, title brevity, restraint on times/reminders, the repeating-task alternative, and the undo path. The most consequential constraint (single batched call) is front-loaded.

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 single-parameter batch-write tool with no output schema, the definition covers batching, field policy, side effects, and reversibility. What it returns (e.g., created task identifiers for later update/delete) is not stated, which is the remaining gap.

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?

Top-level schema coverage is reported as 0%, so the description compensates with policy guidance: keep titles short like a to-do item, and only supply a time or reminder when the user gave one or clearly wants one. It does not explain the dayKey/backlog semantics or when to prefer reminderAt over reminderMinutesBefore, though those nested fields are documented in the schema itself.

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 and resource (add one-off tasks), the batch ceiling (up to 50 in one call), and explicitly names the sibling it is not for (add_repeating_task). An agent can distinguish it from add_repeating_task or update_tasks without opening any schema.

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?

Gives positive when-to-use guidance (batch a whole week or several days into one call), an explicit exclusion with the correct alternative (repeating every day/week → add_repeating_task), and a recovery path (undo_last_change). Very little is left to inference.

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