Skip to main content
Glama
claus-92

Super Productivity MCP Server

by claus-92

get_task

Retrieve the full details of a task by supplying its task ID. Returns title, description, status, and other attributes.

Instructions

Returns details of a specific task by ID.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesTask ID

Implementation Reference

  • The get_task tool handler: registered via server.tool(), extracts the Task by ID via SpClient.getTask(id) and returns the result.
    // ── Get single task ─────────────────────────────────────────────────────
    server.tool(
      "get_task",
      "Returns details of a specific task by ID.",
      { id: z.string().describe("Task ID") },
      async ({ id }) => {
        const task = await SpClient.getTask(id);
        return ok(task);
      }
    );
  • Registration of the 'get_task' tool: server.tool('get_task', ...) inside registerTaskTools().
    // ── Get single task ─────────────────────────────────────────────────────
    server.tool(
      "get_task",
      "Returns details of a specific task by ID.",
      { id: z.string().describe("Task ID") },
      async ({ id }) => {
        const task = await SpClient.getTask(id);
        return ok(task);
      }
    );
  • Schema for get_task: expects a single required 'id' parameter of type z.string().
    "get_task",
    "Returns details of a specific task by ID.",
    { id: z.string().describe("Task ID") },
  • SpClient.getTask(id): sends GET /tasks/{id} and parses the response with TaskSchema.
    getTask(id: string): Promise<Task> {
      return request(`/tasks/${id}`, TaskSchema);
    },
  • src/index.ts:16-16 (registration)
    Top-level registration: registerTaskTools(server) is called from the entry point.
    registerTaskTools(server);
Behavior2/5

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

No annotations are provided, so the description must convey behavioral traits. It only states 'returns details' without specifying what details are included, whether the operation is read-only, or any prerequisites. For a read operation, basic behavioral context is missing.

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?

A single sentence is concise and front-loaded. It efficiently conveys the purpose, though it could be slightly expanded without losing conciseness. No unnecessary words.

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?

With no output schema and 14 sibling tools, the description lacks completeness. It fails to hint at the structure of returned details or how this tool differs from search_tasks or get_current_task. More context is needed for effective selection.

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?

Input schema has 1 parameter with 100% coverage. The description adds 'by ID' but this is largely redundant with the schema's description 'Task ID'. No additional semantic value beyond the schema is provided.

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 verb (returns), the resource (details of a specific task), and the mechanism (by ID). It effectively distinguishes from sibling tools like list_tasks (returns multiple tasks) or modify tools like archive_task.

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 usage when needing details of a known task, but lacks explicit guidance on when to use this vs alternatives like get_current_task or search_tasks. No exclusions or when-not-to-use are provided.

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