Skip to main content
Glama
claus-92

Super Productivity MCP Server

by claus-92

archive_task

Archives a task by its ID, moving it from active view to the archive for organized task management.

Instructions

Archives a task.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesTask ID

Implementation Reference

  • The archive_task tool handler: defines the schema (id: string), calls SpClient.archiveTask(id), and returns the result.
    server.tool(
      "archive_task",
      "Archives a task.",
      { id: z.string().describe("Task ID") },
      async ({ id }) => {
        const task = await SpClient.archiveTask(id);
        return ok(task);
      }
  • The SpClient.archiveTask() method that performs the actual HTTP request to POST /tasks/{id}/archive
    archiveTask(id: string): Promise<Task> {
      return request(`/tasks/${id}/archive`, TaskSchema, {
        method: "POST",
      });
    },
  • src/index.ts:5-17 (registration)
    The tool registration entry point: registerTaskTools(server) is called in index.ts which registers all task tools including archive_task on the MCP server.
    import { registerTaskTools } from "./tools/tasks.js";
    import { registerProjectTools } from "./tools/projects.js";
    import { registerResources } from "./resources.js";
    import { registerPrompts } from "./prompts.js";
    
    const server = new McpServer({
      name: "super-productivity-mcp",
      version: "1.0.0",
    });
    
    // Register everything
    registerTaskTools(server);
    registerProjectTools(server);
Behavior1/5

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

With no annotations and a one-line description, critical behavioral traits (e.g., reversibility, permissions, side effects) are entirely absent. The description does not disclose what 'archiving' implies beyond the verb itself.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence, making it concise. However, it is under-specified for an archive operation, lacking any structural elements like front-loading key behavior.

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 simplicity of the tool (one parameter, no output schema), the description should still clarify what archiving means and how it differs from sibling operations. It fails to provide sufficient context for an agent.

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 description coverage is 100% for the only parameter 'id', which has a basic description 'Task ID'. The tool description adds no extra semantics, so it meets the baseline but does not compensate beyond what the schema provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Archives a task' is essentially a tautology of the tool name 'archive_task', providing minimal clarification. It states the action and resource but adds no value beyond the name itself, making it barely informative.

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 is provided on when to use this tool versus alternatives like delete_task or complete_task. The description lacks any contextual cues for selection.

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