Skip to main content
Glama

score_checklist_item

Toggle a checklist item between complete and incomplete by specifying the task ID and item ID. Use this to mark progress on subtasks within a Habitica task.

Instructions

Toggle a checklist item complete/incomplete.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
taskIdYes
itemIdYes

Implementation Reference

  • index.js:202-213 (registration)
    Registration of the 'score_checklist_item' tool with its name, description, and inputSchema (taskId, itemId).
    {
      name: "score_checklist_item",
      description: "Toggle a checklist item complete/incomplete.",
      inputSchema: {
        type: "object",
        properties: {
          taskId: { type: "string" },
          itemId: { type: "string" },
        },
        required: ["taskId", "itemId"],
      },
    },
  • Handler function for score_checklist_item. Calls the Habitica API POST endpoint to toggle a checklist item's completion status.
    score_checklist_item: async ({ taskId, itemId }) => {
      await api("POST", `/tasks/${taskId}/checklist/${itemId}/score`);
      return ok(`Toggled checklist item ${itemId}.`);
    },
Behavior2/5

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

The description lacks behavioral details beyond stating the toggle action. With no annotations, it should disclose whether toggling is idempotent, what happens when already complete/incomplete, or any side effects like updating task progress. The current text is too minimal.

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?

The description is extremely concise with no wasted words. However, it could include a brief explanation of parameters without losing brevity, such as specifying that 'taskId' is the parent task and 'itemId' is the checklist item.

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?

For a simple tool with two parameters and no output schema, the description is too sparse. It does not clarify the nature of 'taskId' and 'itemId', nor does it explain the result of toggling or any cascading effects, making it insufficient for a new agent.

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 input schema has two parameters (taskId, itemId) with zero schema description coverage. The tool description does not explain what these parameters represent or how they should be used, leaving the agent with no semantic clues.

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 action ('toggle') and the target resource ('checklist item'), with an explicit outcome ('complete/incomplete'). It distinguishes from siblings like 'add_checklist_item' and 'delete_checklist_item' by focusing on state toggling.

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 is provided on when to use this tool versus alternatives such as 'update_checklist_item' or 'score_task'. The description does not specify any prerequisites, limitations, or context for switching between tools.

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