Skip to main content
Glama

Mark Done

mark_done

Mark cards as completed in Codecks project management by providing their UUIDs to update task status.

Instructions

Mark cards as done.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
card_idsYesFull 36-char UUIDs

Implementation Reference

  • Tool registration for 'mark_done' with input schema (card_ids array) and handler that validates UUIDs and calls client.markDone()
    server.registerTool(
      "mark_done",
      {
        title: "Mark Done",
        description: "Mark cards as done.",
        inputSchema: z.object({
          card_ids: z.array(z.string()).describe("Full 36-char UUIDs"),
        }),
      },
      async (args) => {
        try {
          validateUuidList(args.card_ids);
          const result = await client.markDone(args.card_ids);
          return {
            content: [{ type: "text", text: JSON.stringify(finalizeToolResult(result)) }],
          };
        } catch (err) {
          return {
            content: [
              {
                type: "text",
                text: JSON.stringify(finalizeToolResult(handleError(err))),
              },
            ],
          };
        }
      },
    );
  • Implementation of markDone method that delegates to updateCards with status='done'
    async markDone(cardIds: string[]): Promise<Record<string, unknown>> {
      return this.updateCards({ cardIds, status: "done" });
    }
  • Core updateCards implementation that iterates through cardIds and dispatches 'cards/update' API calls for each card
    async updateCards(options: {
      cardIds: string[];
      status?: string;
      priority?: string;
      effort?: string;
      deck?: string;
      title?: string;
      content?: string;
      milestone?: string;
      hero?: string;
      owner?: string;
      tags?: string;
      doc?: string;
      continueOnError?: boolean;
    }): Promise<Record<string, unknown>> {
      const updates: Record<string, unknown> = {};
      if (options.status) updates.status = options.status;
      if (options.priority) {
        updates.priority = options.priority === "null" ? null : options.priority;
      }
      if (options.effort) {
        updates.effort = options.effort === "null" ? null : parseInt(options.effort, 10);
      }
      if (options.title) updates.title = options.title;
      if (options.content !== undefined) updates.content = options.content;
    
      const results: Record<string, unknown>[] = [];
      let updated = 0;
    
      for (const cardId of options.cardIds) {
        try {
          const r = await dispatch("cards/update", {
            cardId,
            update: updates,
          });
          results.push({ card_id: cardId, ok: true, result: r });
          updated++;
        } catch (err) {
          const msg = err instanceof Error ? err.message : String(err);
          results.push({ card_id: cardId, ok: false, error: msg });
          if (!options.continueOnError) break;
        }
      }
    
      return { ok: updated > 0, updated, results };
    }
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. 'Mark cards as done' implies a mutation operation, but it doesn't specify whether this is reversible, what permissions are required, if it triggers notifications, or how it affects card state (e.g., moves to a 'done' lane). The description provides minimal behavioral context beyond the basic action.

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?

The description is extremely concise at just three words ('Mark cards as done'), with zero wasted language. It's front-loaded with the core action and resource. Every word earns its place in communicating the essential purpose.

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 mutation tool with no annotations and no output schema, the description is incomplete. It doesn't explain what 'done' means operationally, what the tool returns, whether changes are permanent, or error conditions. Given the complexity of state-changing operations and lack of structured metadata, the description should provide more contextual information.

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?

The input schema has 100% description coverage, with the single parameter 'card_ids' documented as 'Full 36-char UUIDs'. The description adds no additional parameter information beyond what the schema provides. According to scoring rules, with high schema coverage (>80%), the baseline is 3 even with no param info in the description.

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 'Mark cards as done' clearly states the action (mark) and resource (cards) with a specific status outcome (done). It distinguishes from sibling tools like 'archive_card' or 'mark_started' by focusing on completion status rather than archiving or starting. However, it doesn't specify what 'done' means in this system context.

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 like 'archive_card' or 'mark_started'. The description doesn't mention prerequisites (e.g., cards must exist, be in a certain state) or exclusions. It's a basic statement with no contextual usage information.

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/rangogamedev/codecks-mcp'

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