Skip to main content
Glama

create_task

Create new tasks in Habitica including habits, dailies, todos, and rewards with options for difficulty, priority, due dates, and checklists.

Instructions

Create a habit, daily, todo, or reward.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeYes
textYesTitle.
notesNoNotes / description.
difficultyNo0.1=trivial, 1=easy, 1.5=medium, 2=hard.
priorityNo0.1=low, 1=med, 1.5=high, 2=urgent.
dateNoDue date for todos (ISO).
valueNoCost in gold for rewards.
checklistNo

Implementation Reference

  • Schema definition for the create_task tool: accepts type (habit/daily/todo/reward), text (required), and optional notes, difficulty, priority, date, value, and checklist.
    {
      name: "create_task",
      description: "Create a habit, daily, todo, or reward.",
      inputSchema: {
        type: "object",
        properties: {
          type: { type: "string", enum: ["habit", "daily", "todo", "reward"] },
          text: { type: "string", description: "Title." },
          notes: { type: "string", description: "Notes / description." },
          difficulty: {
            type: "number",
            enum: [0.1, 1, 1.5, 2],
            description: "0.1=trivial, 1=easy, 1.5=medium, 2=hard.",
          },
          priority: {
            type: "number",
            enum: [0.1, 1, 1.5, 2],
            description: "0.1=low, 1=med, 1.5=high, 2=urgent.",
          },
          date: { type: "string", description: "Due date for todos (ISO)." },
          value: { type: "number", description: "Cost in gold for rewards." },
          checklist: {
            type: "array",
            items: {
              type: "object",
              properties: {
                text: { type: "string" },
                completed: { type: "boolean", default: false },
              },
              required: ["text"],
            },
          },
        },
        required: ["type", "text"],
      },
    },
  • Handler for create_task: sends a POST request to /tasks/user with the provided args, then returns a success message with the task type, title, and ID.
    create_task: async (args) => {
      const t = (await api("POST", "/tasks/user", args)).data;
      return ok(`Created ${t.type}: "${t.text}" (id: ${t.id})`);
    },
  • index.js:482-492 (registration)
    Generic tool call handler that dispatches to handlers[name], which includes create_task when name matches.
    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, the description must disclose behavioral traits. It merely states creation without mentioning side effects, permissions, or data modifications. The minimal description fails to provide essential behavioral context for a mutation tool.

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 a single, front-loaded sentence with no filler. It could benefit from slight expansion, but currently it is efficiently concise and immediately conveys the core functionality.

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 8 parameters, no output schema, and sibling tools, the description is insufficient. It does not explain differences between task types, behavior of creating habits vs. dailies, or interaction with existing tasks. The description is complete only for the most basic understanding.

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 description coverage is 75%, so the schema already documents most parameters. The description adds no new semantic value beyond listing task types, which is already implied by the 'type' enum. Baseline 3 is appropriate.

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 explicitly states the tool creates a habit, daily, todo, or reward, clearly identifying the verb and resource. It distinguishes from siblings like update_task or delete_task by specifying the action and task types.

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 given on when to use this tool versus alternatives (e.g., buy_item, score_task). The description lacks context on prerequisites or exclusions, leaving the agent to guess appropriate usage 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