Skip to main content
Glama

get_task

Retrieve a full Kanboard task by its numeric ID, including status, dates, column, swimlane, and metadata. Returns NOT_FOUND if the task does not exist.

Instructions

Retrieve a single Kanboard task by its numeric id. Returns the full task entity including status, dates, column, swimlane, and metadata. Returns NOT_FOUND when the task does not exist.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
task_idYesThe task id to retrieve (must be a positive integer).

Implementation Reference

  • The get_task tool definition and handler function. Parses input via GetTaskInput schema, calls deps.handler.getTask(), and returns the task as JSON content plus structured object.
    export const getTaskTool = {
      name: "get_task",
      description:
        "Retrieve a single Kanboard task by its numeric id. " +
        "Returns the full task entity including status, dates, column, swimlane, and metadata. " +
        "Returns NOT_FOUND when the task does not exist.",
      inputSchema: GetTaskInput,
      handler: async (raw: unknown, deps: ToolDeps): Promise<GetTaskResult> => {
        const input = GetTaskInput.parse(raw);
        const task = await deps.handler.getTask(input.task_id);
    
        return {
          content: [{ type: "text", text: JSON.stringify(task, null, 2) }],
          structuredContent: task,
        };
      },
    };
  • Zod input schema for get_task: requires a positive integer task_id, strict mode.
    export const GetTaskInput = z
      .object({
        task_id: z.number().int().positive().describe("The task id to retrieve (must be a positive integer)."),
      })
      .strict();
  • KanboardHandler.getTask() helper method that calls the Kanboard API client with 'getTask' JSON-RPC method and decodes the result via TaskSchema.
    public async getTask(taskId: number): Promise<Task> {
      const raw = await this.#apiClient.call("getTask", { task_id: taskId });
      this.#logger.debug({ method: "getTask" }, "getTask OK");
      return decodeGetSingle("getTask", raw, TaskSchema, this.#logger);
    }
  • Import of getTaskTool from ./get-task.js into the central tools index.
    import { getTaskTool } from "./get-task.js";
  • Re-export of getTaskTool from the central tools barrel module.
    export { getTaskTool } from "./get-task.js";
Behavior4/5

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

Discloses return value (full task entity with fields) and error case (NOT_FOUND). Without annotations, this adds essential behavioral info. Could mention idempotency, but not required.

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?

Two concise sentences, front-loaded with verb and resource. No unnecessary words. Every sentence adds value.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple retrieval tool with one parameter and no output schema, the description covers purpose, return value, and error case. No critical gaps given the tool's simplicity.

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% with parameter description. Description adds context about the task entity but does not expand on the parameter itself beyond the schema. Baseline score 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?

Clearly states the action ('Retrieve'), the resource ('single Kanboard task'), and distinguishes from siblings (by numeric id, returns full entity). The mention of NOT_FOUND further clarifies behavior.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Describes the use case for retrieving a single task by ID. While it does not explicitly exclude siblings like list_tasks, the context is clear. Could be improved by noting when not to use it (e.g., for bulk retrieval).

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/ErnestoCorona/kanboard-mcp'

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