Skip to main content
Glama
routineco

Routine

Official
by routineco

taskComplete

Mark tasks as completed in Routine by specifying the task ID. Streamline your productivity by managing task statuses directly through the MCP server.

Instructions

Complete a task.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes

Implementation Reference

  • Handler function that executes the taskComplete tool: takes task ID, sends RPC request to 'task.complete', returns JSON response or error.
    async ({ id }) => {
      try {
        const data = await sendRpcRequest("task.complete", [id]);
        return {
          content: [{ type: "text", text: JSON.stringify(data, null, 2) }],
        };
      } catch (error) {
        logger.error("Error fetching task.complete: %o", error);
        return {
          content: [
            {
              type: "text",
              text: `Error fetching auth id: ${error instanceof Error ? error.message : String(error)}`,
            },
          ],
          isError: true,
        };
      }
    }
  • Input schema for taskComplete tool: requires a string 'id' for the task ID, validated with Zod.
          /*
    {"$id":"#task-id","$schema":"https://json-schema.org/draft/2019-09/schema","type":"string"}
    */ id: z.string(),
        },
  • src/tools.ts:286-312 (registration)
    Registration of the taskComplete tool via server.tool call, including name, description, input schema, and handler function.
        "taskComplete",
        "Complete a task.",
        {
          /*
    {"$id":"#task-id","$schema":"https://json-schema.org/draft/2019-09/schema","type":"string"}
    */ id: z.string(),
        },
        async ({ id }) => {
          try {
            const data = await sendRpcRequest("task.complete", [id]);
            return {
              content: [{ type: "text", text: JSON.stringify(data, null, 2) }],
            };
          } catch (error) {
            logger.error("Error fetching task.complete: %o", error);
            return {
              content: [
                {
                  type: "text",
                  text: `Error fetching auth id: ${error instanceof Error ? error.message : String(error)}`,
                },
              ],
              isError: true,
            };
          }
        }
      );
Behavior1/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure but offers none. 'Complete a task' implies a mutation operation but doesn't specify what completion means (marking as done, archiving, changing status), whether it's reversible (note the 'taskUncomplete' sibling exists), what permissions are required, or what the response contains. For a mutation tool with zero annotation coverage, this is completely inadequate.

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 maximally concise at just three words. While severely under-specified, it contains no redundant or unnecessary language. Every word ('Complete', 'a', 'task') contributes directly to the core purpose statement without any fluff or structural issues.

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

Completeness1/5

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

Given this is a mutation tool (completing tasks) with no annotations, 0% schema description coverage, no output schema, and multiple sibling tools, the description is completely inadequate. It doesn't explain what completion means, how it differs from other task operations, what the parameter represents, what happens after completion, or any behavioral aspects. The description fails to provide the minimal context needed for effective tool use.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema has 0% description coverage for its single required 'id' parameter, and the tool description provides absolutely no information about parameters. The description doesn't mention the 'id' parameter at all, nor does it explain what format the ID should be, where to obtain it, or what task it refers to. With zero schema coverage and no parameter information in the description, this fails to provide basic parameter semantics.

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 'Complete a task' is a tautology that essentially restates the tool name 'taskComplete' without adding meaningful specificity. While it indicates the verb 'complete' and resource 'task', it doesn't distinguish this tool from its sibling 'taskUncomplete' or explain what completion entails. This minimal description provides only basic purpose information without differentiation.

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?

The description provides no guidance on when to use this tool versus alternatives. With siblings like 'taskUncomplete', 'taskUpdate', and 'taskCreateSimple' available, there's no indication of when completion is appropriate versus updating or creating tasks. The description lacks any context about prerequisites, timing considerations, or relationships to other task operations.

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

Related 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/routineco/mcp-server'

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