Skip to main content
Glama

update_checklist_item

Update the text or completion status of a checklist item inside a task. Manage subtask progress accurately.

Instructions

Update text/completed on a checklist item.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
taskIdYes
itemIdYes
textNo
completedNo

Implementation Reference

  • Input schema definition for update_checklist_item tool. Defines required params: taskId, itemId, and optional params: text (string) and completed (boolean).
    {
      name: "update_checklist_item",
      description: "Update text/completed on a checklist item.",
      inputSchema: {
        type: "object",
        properties: {
          taskId: { type: "string" },
          itemId: { type: "string" },
          text: { type: "string" },
          completed: { type: "boolean" },
        },
        required: ["taskId", "itemId"],
      },
    },
  • Handler function for update_checklist_item. Makes a PUT request to /tasks/{taskId}/checklist/{itemId} with the updates object (spread from rest params).
    update_checklist_item: async ({ taskId, itemId, ...updates }) => {
      await api("PUT", `/tasks/${taskId}/checklist/${itemId}`, updates);
      return ok(`Updated checklist item ${itemId}.`);
    },
  • index.js:188-201 (registration)
    The tool is registered in the tools[] array (line 58-367) alongside all other tools. The ListToolsRequestSchema handler at line 480 returns this array.
    {
      name: "update_checklist_item",
      description: "Update text/completed on a checklist item.",
      inputSchema: {
        type: "object",
        properties: {
          taskId: { type: "string" },
          itemId: { type: "string" },
          text: { type: "string" },
          completed: { type: "boolean" },
        },
        required: ["taskId", "itemId"],
      },
    },
  • The api() helper function used by the handler to make HTTP requests to the Habitica API.
    async function api(method, path, body) {
      const url = `${API_BASE}${path}`;
      const headers = {
        "x-api-user": USER_ID,
        "x-api-key": API_TOKEN,
        "x-client": `${USER_ID}-${APP_ID}`,
        "Content-Type": "application/json",
      };
      const res = await fetch(url, {
        method,
        headers,
        body: body === undefined ? undefined : JSON.stringify(body),
      });
      const text = await res.text();
      let payload;
      try {
        payload = text ? JSON.parse(text) : {};
      } catch {
        payload = { raw: text };
      }
      if (!res.ok) {
        const msg = payload?.message || payload?.error || res.statusText;
        throw new McpError(
          ErrorCode.InternalError,
          `Habitica API ${res.status}: ${msg}`,
        );
      }
      return payload;
    }
Behavior2/5

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

No annotations provided. Description indicates mutation ('Update') but does not disclose side effects, permission requirements, or return behavior. Minimal transparency.

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?

Single sentence front-loads the key information, no redundant words. Efficient and direct.

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 4 parameters, no output schema, and no annotations, the description is incomplete. Missing details on required identifiers, optionality of fields, and return value.

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 coverage is 0%, but description adds meaning by naming the updatable fields ('text/completed'). Does not clarify taskId and itemId as identifiers, but partially compensates for missing schema descriptions.

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?

Description clearly states the action 'Update' and the resource 'checklist item', specifying the fields 'text/completed'. This distinguishes it from sibling tools like add_checklist_item and delete_checklist_item.

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 on when to use this tool versus alternatives like score_checklist_item or update_task. No context on prerequisites or scenarios.

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/leon-jarvis1/habitca_mcp'

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