Skip to main content
Glama

add_task

Append an open checkbox task to Claude/Tasks.md in Obsidian Tasks plugin format, with an optional YYYY-MM-DD due date.

Instructions

Append an open checkbox task to Claude/Tasks.md, in the format the Obsidian Tasks plugin reads. due is optional and must be YYYY-MM-DD.

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": {
      "content": "<content>"
    },
    "name": "add_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
dueNo
contentYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.1

TDQS

A4/5.0
Behavior3/5

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

With no annotations supplied, the description does carry real behavioral weight: it discloses the target file, that entries are appended rather than overwriting, that the task is created open, and that the line format is Obsidian Tasks-compatible. It does not say what happens if the file or directory is missing, whether duplicates are checked, or whether anything else in the file is touched — notable omissions for a write tool with zero annotation coverage, though the presence of an output schema relieves it of describing return values.

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?

Two sentences, both front-loaded with the essential information (destination and format first, then the parameter constraint). No filler or restatement of the tool name.

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 append tool with an output schema available, the definition covers destination, file format, and the one non-obvious parameter rule. The remaining gap is failure/edge behavior (missing file, duplicate tasks), which matters for a writer but is a modest omission here.

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 coverage is 0%, so the description must compensate, and it does for `due`: it states the parameter is optional and constrains the format to YYYY-MM-DD, which the schema does not express. `content` is only implied via 'open checkbox task' — it is not clarified whether the caller passes plain task text or full checkbox syntax — which keeps this short of a 5.

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?

Names a specific verb (append) plus the exact resource and destination: an open checkbox task in Claude/Tasks.md. The mention of the Obsidian Tasks plugin format further pins down the output shape, and the append-only nature clearly separates it from read-side siblings like list_tasks.

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?

The description implies when to use it (creating a new open task) but never states when not to, nor points to an alternative such as list_tasks for reading or write_note/capture for free-form text. An agent can infer the intent, but there is no explicit routing guidance.

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