Skip to main content
Glama
dragosroua

addTaskManager MCP Server

by dragosroua

do_mark_task_as_done

Mark tasks as completed in the Do realm of the ADD framework to track progress and manage workflow.

Instructions

Mark tasks as completed in Do realm.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
taskRecordNameYesTask record name

Implementation Reference

  • src/index.ts:523-534 (registration)
    Tool registration in ListToolsRequestSchema handler, including name, description, and input schema definition.
    {
      name: 'do_mark_task_as_done',
      description: 'Mark tasks as completed in Do realm.',
      inputSchema: {
        type: 'object',
        properties: {
          taskRecordName: { type: 'string', description: 'Task record name' }
        },
        required: ['taskRecordName']
      }
    },
    {
  • src/index.ts:732-734 (registration)
    Tool dispatch in CallToolRequestSchema switch statement, validating arguments and calling the handler.
    case 'do_mark_task_as_done':
      this.validateArgs(args, ['taskRecordName']);
      return await this.markTaskAsDone(args.taskRecordName);
  • The handler function that implements the tool logic. Validates the task is in Do realm (3), then mocks completion by returning a success message indicating endDate set and moved to realm 4 (Done).
    private async markTaskAsDone(taskRecordName: string) {
      // Validate that task is in Do realm before marking as done
      const item = await this.mockFetchItem(taskRecordName, 'Task');
      if (!item) {
        throw new McpError(ErrorCode.InvalidParams, `Task ${taskRecordName} not found`);
      }
      if (item.realmId !== REALM_DO_ID) {
        throw new McpError(ErrorCode.InvalidParams, `Task ${taskRecordName} must be in Do realm to mark as done. Current realm: ${item.realmId}. Move to Do realm first.`);
      }
      
      const completionTime = new Date().toISOString();
      // Mock marking task as done via CloudKit - this would set realmId to 4 (Done) and move to Done collection
      return { content: [{ type: 'text', text: `Task ${taskRecordName} marked as done at ${completionTime}. Moved to Done collection (realm 4).` }] };
    }
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool marks tasks as completed, implying a mutation operation, but doesn't disclose critical details like whether this requires specific permissions, if changes are reversible, what happens to task status, or error conditions. This is a significant gap for a mutation tool with zero annotation coverage.

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, efficient sentence that directly states the tool's purpose without unnecessary words. It is appropriately sized for a simple tool, though it could be slightly more informative without losing conciseness.

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 the tool's complexity (a mutation operation with no annotations and no output schema), the description is incomplete. It lacks behavioral details, usage context, and output information, making it inadequate for an agent to confidently invoke the tool without additional assumptions or errors.

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 100%, with the single parameter 'taskRecordName' documented in the schema. The description adds no additional parameter semantics beyond what the schema provides, such as format examples or constraints. With high schema coverage, the baseline score of 3 is appropriate as the description doesn't compensate but also doesn't detract.

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 action ('Mark tasks as completed') and the target ('in Do realm'), which is a specific verb+resource combination. It distinguishes from siblings like 'do_mark_project_as_done' by specifying 'tasks' vs 'project', but doesn't fully differentiate from other task-related tools like 'assess_edit_task' or 'decide_move_task_to_do' in terms of purpose.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., tasks must be in the 'Do' realm), exclusions, or comparisons to sibling tools like 'assess_edit_task' or 'decide_move_task_to_do', leaving the agent to infer usage context.

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/dragosroua/addtaskmanager-mcp-server'

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