Skip to main content
Glama

board_get_task

Retrieve a single task's complete record by providing its ID. Returns all fields including status, priority, and timestamps; returns error if task does not exist.

Instructions

Fetch a single task by its ID. Use this when you have a task ID (from board_create_task, a handoff note, or an activity_log entry) and need the full task record — for listing many tasks under a project, use board_get_tasks instead. Returns every field: id, project_id, title, description, status, priority, assigned_agent, parent_task_id, depends_on, riper_mode, metadata, and ISO timestamps (created_at, updated_at, started_at, completed_at). Returns { error } when the task doesn't exist rather than throwing — callers should check for the error key before treating the result as a task.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
task_idYesTask ID to fetch. Get this from the response of board_create_task, from handoff notes, or from activity_log entries.

Implementation Reference

  • The handler function for the 'board_get_task' tool. Fetches a single task by its ID from Firestore. Queries the 'tasks' collection by document ID, returns {error} if not found, otherwise returns all task fields with ISO timestamp conversions.
    server.tool(
      "board_get_task",
      "Fetch a single task by its ID. Use this when you have a task ID (from board_create_task, a handoff note, or an activity_log entry) and need the full task record — for listing many tasks under a project, use board_get_tasks instead. Returns every field: id, project_id, title, description, status, priority, assigned_agent, parent_task_id, depends_on, riper_mode, metadata, and ISO timestamps (created_at, updated_at, started_at, completed_at). Returns { error } when the task doesn't exist rather than throwing — callers should check for the error key before treating the result as a task.",
      {
        task_id: z.string().describe("Task ID to fetch. Get this from the response of board_create_task, from handoff notes, or from activity_log entries."),
      },
      async ({ task_id }) => {
        const snap = await db.collection("tasks").doc(task_id).get();
        if (!snap.exists) {
          return {
            content: [
              {
                type: "text" as const,
                text: JSON.stringify({ error: `Task ${task_id} not found` }),
              },
            ],
          };
        }
        const data = snap.data() ?? {};
        const toISO = (v: unknown) =>
          v && typeof v === "object" && "toDate" in (v as object)
            ? (v as { toDate(): Date }).toDate().toISOString()
            : null;
        const task = {
          id: snap.id,
          ...data,
          created_at: toISO((data as Record<string, unknown>).created_at),
          updated_at: toISO((data as Record<string, unknown>).updated_at),
          started_at: toISO((data as Record<string, unknown>).started_at),
          completed_at: toISO((data as Record<string, unknown>).completed_at),
        };
        return {
          content: [
            { type: "text" as const, text: JSON.stringify(task, null, 2) },
          ],
        };
      }
    );
  • Input schema for board_get_task: requires a single 'task_id' string parameter.
    {
      task_id: z.string().describe("Task ID to fetch. Get this from the response of board_create_task, from handoff notes, or from activity_log entries."),
    },
  • Registration of 'board_get_task' via server.tool() inside the registerTaskTools function, which is called from src/index.ts line 29.
    server.tool(
      "board_get_task",
      "Fetch a single task by its ID. Use this when you have a task ID (from board_create_task, a handoff note, or an activity_log entry) and need the full task record — for listing many tasks under a project, use board_get_tasks instead. Returns every field: id, project_id, title, description, status, priority, assigned_agent, parent_task_id, depends_on, riper_mode, metadata, and ISO timestamps (created_at, updated_at, started_at, completed_at). Returns { error } when the task doesn't exist rather than throwing — callers should check for the error key before treating the result as a task.",
      {
        task_id: z.string().describe("Task ID to fetch. Get this from the response of board_create_task, from handoff notes, or from activity_log entries."),
      },
      async ({ task_id }) => {
        const snap = await db.collection("tasks").doc(task_id).get();
        if (!snap.exists) {
          return {
            content: [
              {
                type: "text" as const,
                text: JSON.stringify({ error: `Task ${task_id} not found` }),
              },
            ],
          };
        }
        const data = snap.data() ?? {};
        const toISO = (v: unknown) =>
          v && typeof v === "object" && "toDate" in (v as object)
            ? (v as { toDate(): Date }).toDate().toISOString()
            : null;
        const task = {
          id: snap.id,
          ...data,
          created_at: toISO((data as Record<string, unknown>).created_at),
          updated_at: toISO((data as Record<string, unknown>).updated_at),
          started_at: toISO((data as Record<string, unknown>).started_at),
          completed_at: toISO((data as Record<string, unknown>).completed_at),
        };
        return {
          content: [
            { type: "text" as const, text: JSON.stringify(task, null, 2) },
          ],
        };
      }
    );
Behavior5/5

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

Without annotations, description fully discloses behavior: returns every field (listed), returns { error } on missing task instead of throwing, and advises callers to check for error key.

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?

Front-loaded with purpose, uses clear structure. The field listing is necessary due to no output schema, and the description is efficient without waste.

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 single-fetch tool with one parameter and no output schema, the description covers return format, error handling, and use case completely.

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?

Description largely echoes the schema's parameter description ('Task ID to fetch...'). While it adds context on usage, it does not provide significantly new semantics beyond the schema, so baseline 3.

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?

Description clearly states 'Fetch a single task by its ID', specifies verb and resource, and distinguishes from sibling board_get_tasks which lists many tasks.

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

Usage Guidelines5/5

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

Explicitly tells when to use (when you have a task ID and need full record) and when not to (for listing many, use board_get_tasks). Also provides sources for obtaining the ID.

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/HuntsDesk/ve-vibe-board'

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