Akiflow MCP Server

remove-task-from-timeslot

Unlink a task from its scheduled time slot block to free up the time for other activities.

Instructions

Remove a task from its time slot. Unlinks the task from its associated time slot block.

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>"
    },
    "name": "remove-task-from-timeslot"
  }
}

Input Schema

Name	Required	Description	Default
`task_id`	Yes	Task UUID to remove from its time slot

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.1May 29, 2026

TDQS

A3.8/5.0

Behavior3/5

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

No annotations provided, so the description must carry behavioral disclosure. It states the operation is to remove/unlink, but does not mention side effects (e.g., what happens to the timeslot), reversibility, or required permissions. For a simple tool, it is minimally transparent.

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, 16 words total, with no redundancy. Every phrase adds value: the first sentence states the action, the second clarifies the effect. Highly efficient.

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, simple action tool with no annotations and no output schema, the description is nearly complete. However, it could briefly mention what the operation does to the timeslot (e.g., whether the timeslot becomes empty) to improve completeness.

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% with one parameter fully described as 'Task UUID to remove from its time slot'. The description adds no additional meaning beyond the schema, so a baseline of 3 is appropriate.

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?

The description clearly states the action ('Remove', 'Unlinks') and the resource ('a task from its time slot', 'its associated time slot block'). It distinguishes from siblings like 'add-task-to-timeslot' which does the opposite.

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?

No explicit guidance on when to use this tool vs alternatives like 'unschedule-task' or 'add-task-to-timeslot'. The description implies usage for unlinking but lacks context on prerequisites or conditions.

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