Skip to main content
Glama
claus-92

Super Productivity MCP Server

by claus-92

start_task

Activate a task as the current working task by specifying its ID, allowing time tracking and status updates.

Instructions

Starts the specified task and makes it the current task.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesTask ID

Implementation Reference

  • The core API handler that sends a POST request to /tasks/{id}/start on the Super Productivity local REST API to start a task.
    startTask(id: string): Promise<Task> {
      return request(`/tasks/${id}/start`, TaskSchema, {
        method: "POST",
      });
    },
  • Input schema for the start_task tool: expects a single string 'id' parameter for the task ID.
    { id: z.string().describe("Task ID") },
  • Registration of the 'start_task' MCP tool via server.tool() with its description, input schema (id: string), and handler that calls SpClient.startTask(id).
    server.tool(
      "start_task",
      "Starts the specified task and makes it the current task.",
      { id: z.string().describe("Task ID") },
      async ({ id }) => {
        const task = await SpClient.startTask(id);
        return ok(task);
      }
    );
  • src/index.ts:16-16 (registration)
    Top-level registration: registerTaskTools is called with the MCP server instance to register all task-related tools including start_task.
    registerTaskTools(server);
Behavior2/5

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

No annotations provided, so the description must disclose behaviors. It only states the core action without mentioning side effects (e.g., state changes, conflicts with current task, persistence, or error conditions). The agent lacks behavioral expectations beyond the action itself.

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?

Single sentence, 10 words, front-loading the verb and resource. No redundancy, but could be slightly more informative without losing conciseness.

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

Completeness2/5

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

Given the action-oriented nature (no output schema, no annotations), the description omits important context: what happens if task is already running, if it fails, or what the response indicates. Sibling tools further highlight the need for distinctions, which are missing.

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 baseline 3. The description does not add parameter-level semantics beyond 'Task ID' from the schema. No additional nuance or constraints are provided.

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 clearly states the verb 'starts' and resource 'specified task', and adds 'makes it the current task' which distinguishes from basic start. However, it does not explicitly differentiate from sibling tools like set_current_task, though the combination of verb and resource is specific.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use start_task versus siblings like set_current_task or archive_task. No prerequisites, conditions, or exclusions are mentioned, leaving the agent to infer usage context.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/claus-92/super-productivity-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server