Skip to main content
Glama

get_tasks

Retrieve a list of tasks from Habitica, with optional type filters for habits, dailies, todos, rewards, or completed todos, helping you manage your game-based productivity.

Instructions

List tasks. Optionally filter by type.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeNoOptional task-type filter.

Implementation Reference

  • Tool schema definition for get_tasks, declaring an optional 'type' parameter to filter tasks.
      name: "get_tasks",
      description: "List tasks. Optionally filter by type.",
      inputSchema: {
        type: "object",
        properties: {
          type: {
            type: "string",
            enum: ["habits", "dailys", "todos", "rewards", "completedTodos"],
            description: "Optional task-type filter.",
          },
        },
      },
    },
  • Handler function for get_tasks: calls Habitica GET /tasks/user with optional type query param and returns JSON response.
    get_tasks: async ({ type } = {}) => {
      const path = type ? `/tasks/user?type=${encodeURIComponent(type)}` : "/tasks/user";
      return json((await api("GET", path)).data);
    },
  • index.js:480-480 (registration)
    Registration via ListToolsRequestSchema: the tools array (including get_tasks definition) is returned to the client.
    server.setRequestHandler(ListToolsRequestSchema, async () => ({ tools }));
  • index.js:482-492 (registration)
    Registration via CallToolRequestSchema: dispatches incoming tool calls to handlers[name], connecting 'get_tasks' to the handler.
    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 should disclose behavioral traits. It only says 'list tasks' implying a read operation, but omits details like no side effects, pagination, or rate limits.

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 very concise with two sentences, front-loading the main action. However, it could include more useful details without being verbose.

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 output schema and no annotations, the description is incomplete. It doesn't mention return format, ordering, or limits, leaving the agent with insufficient context for proper invocation.

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 100%, so the parameter is fully described in the schema. The description adds 'Optionally filter by type', which reinforces but doesn't add new meaning beyond the enum values.

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?

The description clearly states the tool lists tasks with an optional filter, which is a specific verb and resource. While it distinguishes from some siblings like 'get_task' (singular), it doesn't explicitly differentiate from other listing tools.

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 'get_task' for a single task. The description lacks any context about use cases or prerequisites.

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