Skip to main content
Glama

delete_checklist_item

Delete a specific checklist item from a task. Use this action to remove completed or unnecessary entries and keep your task lists organized.

Instructions

Delete a checklist item.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
taskIdYes
itemIdYes

Implementation Reference

  • The handler function that executes the 'delete_checklist_item' tool logic. It calls the Habitica API DELETE endpoint for the checklist item and returns a success message.
    delete_checklist_item: async ({ taskId, itemId }) => {
      await api("DELETE", `/tasks/${taskId}/checklist/${itemId}`);
      return ok(`Deleted checklist item ${itemId}.`);
    },
  • The input schema definition for 'delete_checklist_item'. Defines required string parameters 'taskId' and 'itemId'.
    {
      name: "delete_checklist_item",
      description: "Delete a checklist item.",
      inputSchema: {
        type: "object",
        properties: {
          taskId: { type: "string" },
          itemId: { type: "string" },
        },
        required: ["taskId", "itemId"],
      },
    },
  • index.js:480-492 (registration)
    Tool registration via MCP SDK. The 'tools' array is returned by ListToolsRequestSchema handler, and the 'handlers' object is dispatched by CallToolRequestSchema handler by name lookup.
    server.setRequestHandler(ListToolsRequestSchema, async () => ({ tools }));
    
    server.setRequestHandler(CallToolRequestSchema, async (req) => {
      const { name, arguments: args = {} } = req.params;
      const fn = handlers[name];
      if (!fn) throw new McpError(ErrorCode.MethodNotFound, `Unknown tool: ${name}`);
      try {
        return await fn(args);
      } catch (err) {
        if (err instanceof McpError) throw err;
        throw new McpError(ErrorCode.InternalError, err?.message ?? String(err));
      }
    });
Behavior2/5

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

With no annotations, description must disclose behavior. It only states 'Delete' without mentioning permanence, side effects, or response. Lacks detail for a destructive operation.

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

Conciseness2/5

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

Extremely short, but omits critical details. Conciseness should not sacrifice completeness.

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 no annotations or output schema, the description should provide more context about behavior, prerequisites, and return values. It fails to do so.

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

Parameters2/5

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

Schema has 0% description coverage, and the tool description adds no meaning. Parameter names (taskId, itemId) are suggestive but not explained.

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

Purpose4/5

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

Description clearly states the action (delete) and object (checklist item). However, it lacks context about the relationship to tasks, which is hinted by the sibling tools and input schema.

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 provided on when to use this tool versus alternatives like update_checklist_item or score_checklist_item. Agent has to infer from the action name.

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