Skip to main content
Glama
claus-92

Super Productivity MCP Server

by claus-92

get_current_task

Retrieve the currently active task from Super Productivity. Use this tool to identify the task you are working on at the moment, supporting time management and daily planning.

Instructions

Returns the currently active task, if any.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Tool handler for 'get_current_task' — calls SpClient.getCurrentTask() and returns the result as JSON.
    server.tool(
      "get_current_task",
      "Returns the currently active task, if any.",
      {},
      async () => {
        const task = await SpClient.getCurrentTask();
        return ok(task);
      }
    );
  • src/tools/tasks.ts:1-6 (registration)
    Import statements and the registerTaskTools function that registers 'get_current_task' via server.tool() in the MCP server.
    // src/tools/tasks.ts
    import { McpServer } from "@modelcontextprotocol/sdk/server/mcp.js";
    import { z } from "zod";
    import { SpClient } from "../sp-client.js";
    import { parseIsoDateToTimestamp, resolveProjectId, resolveTagId, resolveTagIds } from "../tool-helpers.js";
  • SpClient.getCurrentTask() — makes a GET request to /task-control/current and returns a Task or null, parsed with TaskSchema.nullable().
    getCurrentTask(): Promise<Task | null> {
      return request("/task-control/current", TaskSchema.nullable());
    },
  • TaskSchema — Zod schema used to validate/parse the task data returned by getCurrentTask().
    const TaskSchema = z.object({
      id: z.string(),
      title: z.string(),
      notes: nullableString,
      projectId: nullableString,
      tagIds: z.array(z.string()).nullish(),
      isDone: z.boolean().default(false),
      timeEstimate: nullableNumber,
      timeSpent: nullableNumber,
      dueDate: nullableNumber,
      created: nullableNumber,
    }).passthrough();
  • src/index.ts:16-16 (registration)
    Server entry point — calls registerTaskTools(server) which registers the 'get_current_task' tool.
    registerTaskTools(server);
Behavior4/5

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

The phrase 'if any' indicates the possibility of no active task, providing transparency. No annotations exist, so the description carries the full burden; it is adequate for a read-only query.

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 description is a single concise sentence with no wasted words, well 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?

Given the tool's simplicity (0 params, no output schema), the description is adequate for an agent to understand its function.

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?

No parameters exist, so the description adds no parameter info. Per instructions, 0 parameters defaults to baseline 4.

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 tool returns the currently active task, distinguishing it from sibling tools like set_current_task and 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?

No explicit usage context is provided, but the tool is a simple query for the current task, so it is self-explanatory.

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