Skip to main content
Glama
routineco

Routine

Official
by routineco

taskUncomplete

Revert a completed task to an incomplete status using Routine's task management system by specifying the task ID.

Instructions

Uncomplete a task.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes

Implementation Reference

  • src/tools.ts:835-861 (registration)
    Registration of the 'taskUncomplete' MCP tool, including inline Zod schema for input (task ID) and the handler function that proxies to the backend RPC 'task.uncomplete'.
        "taskUncomplete",
        "Uncomplete 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.uncomplete", [id]);
            return {
              content: [{ type: "text", text: JSON.stringify(data, null, 2) }],
            };
          } catch (error) {
            logger.error("Error fetching task.uncomplete: %o", error);
            return {
              content: [
                {
                  type: "text",
                  text: `Error fetching auth id: ${error instanceof Error ? error.message : String(error)}`,
                },
              ],
              isError: true,
            };
          }
        }
      );
  • The handler function executes the tool logic by sending an RPC request to 'task.uncomplete' with the task ID and returns the JSON response or an error message.
    async ({ id }) => {
      try {
        const data = await sendRpcRequest("task.uncomplete", [id]);
        return {
          content: [{ type: "text", text: JSON.stringify(data, null, 2) }],
        };
      } catch (error) {
        logger.error("Error fetching task.uncomplete: %o", error);
        return {
          content: [
            {
              type: "text",
              text: `Error fetching auth id: ${error instanceof Error ? error.message : String(error)}`,
            },
          ],
          isError: true,
        };
      }
    }
  • Zod schema for the input parameter 'id' which is a string representing the task ID.
          /*
    {"$id":"#task-id","$schema":"https://json-schema.org/draft/2019-09/schema","type":"string"}
    */ id: z.string(),
        },
Behavior1/5

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

With no annotations provided, the description carries full burden for behavioral disclosure but offers none. 'Uncomplete a task' implies a mutation operation (changing task status), but doesn't specify permissions needed, whether this is reversible, what happens to completion timestamps, or error conditions. It provides zero behavioral context beyond the basic action implied by the name.

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 extremely concise at just three words. While severely under-specified, it's not verbose or repetitive—every word contributes to stating the core action. There's no wasted text, though the brevity comes at the cost of completeness.

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 a mutation tool with no annotations, 1 undocumented parameter, and no output schema, the description is completely inadequate. It doesn't explain what 'uncompleting' means operationally, what the parameter requires, what the tool returns, or how it differs from sibling tools. The agent lacks essential information to use this tool correctly.

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 description mentions no parameters at all, while the schema has 1 required parameter ('id') with 0% description coverage. The description doesn't explain what 'id' represents (task identifier format, source, constraints), leaving the parameter completely undocumented. With low schema coverage and no compensation in the description, this is inadequate.

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 'Uncomplete a task' is a tautology that essentially restates the tool name 'taskUncomplete'. It specifies the verb ('Uncomplete') and resource ('a task'), but doesn't provide any meaningful differentiation from what the name already conveys. It doesn't explain what 'uncompleting' means operationally or how it differs from related operations.

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 about when to use this tool versus alternatives. It doesn't mention prerequisites (like needing a previously completed task), contrast with sibling tools like 'taskComplete' or 'taskUpdate', or indicate appropriate contexts. The agent must infer usage from the name alone.

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