Skip to main content
Glama
dragosroua

addTaskManager MCP Server

by dragosroua

assess_add_task_to_idea

Link an existing task to an idea in the Assess realm to organize tasks within project concepts using the ADD framework.

Instructions

Add an existing task to an idea in Assess realm.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
taskRecordNameYesRecord name of the task
ideaRecordNameYesRecord name of the idea

Implementation Reference

  • The core handler function that implements the tool logic. It simulates adding a task to an idea by returning a mock success message (in production, this would interact with CloudKit to update the idea's 'tasks' reference array).
    private async addTaskToIdea(taskRecordName: string, ideaRecordName: string) {
      // Mock adding task to idea via CloudKit
      return { content: [{ type: 'text', text: `Task ${taskRecordName} added to idea ${ideaRecordName}` }] };
    }
  • src/index.ts:365-376 (registration)
    Tool registration in the ListToolsRequestSchema response, defining the tool name, description, and input schema.
    {
      name: 'assess_add_task_to_idea',
      description: 'Add an existing task to an idea in Assess realm.',
      inputSchema: {
        type: 'object',
        properties: {
          taskRecordName: { type: 'string', description: 'Record name of the task' },
          ideaRecordName: { type: 'string', description: 'Record name of the idea' }
        },
        required: ['taskRecordName', 'ideaRecordName']
      }
    },
  • Dispatch handler in the CallToolRequestSchema switch statement that validates input arguments and invokes the main addTaskToIdea handler function.
    case 'assess_remove_task_from_project':
      this.validateArgs(args, ['taskRecordName', 'projectRecordName']);
      return await this.removeTaskFromProject(args.taskRecordName, args.projectRecordName);
  • Input schema definition for validating tool arguments: requires taskRecordName and ideaRecordName as strings.
    inputSchema: {
      type: 'object',
      properties: {
        taskRecordName: { type: 'string', description: 'Record name of the task' },
        ideaRecordName: { type: 'string', description: 'Record name of the idea' }
      },
      required: ['taskRecordName', 'ideaRecordName']
    }
  • Type definition for Idea records in CloudKit, including the 'tasks' reference array that would be updated when adding a task to an idea.
    export interface ZenTaskticIdea {
      recordName?: string;
      recordType: 'Ideas'; // Note: entity name is 'Ideas' in Core Data
      fields: {
        ideaName: { value: string }; // Max 1500 chars, combines original title & body
        realmId: { value: number }; // Integer 16, default 0 (usually REALM_ASSESS_ID)
        uniqueId: { value: string }; // UUID
        lastModified: { value: number }; // Timestamp
        
        // References (relationships in Core Data)
        collection?: { value: CKReference }; // Reference to Collections record
        realm?: { value: CKReference }; // Reference to Realms record
        tasks?: { value: CKReference[] }; // Tasks derived from this idea
        
        // removed createdAt, use lastModified or CloudKit system creationDate
      };
    }
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 action is 'Add,' implying a mutation, but doesn't describe effects like whether this creates a link, updates statuses, requires permissions, or has side effects. For a mutation tool with zero annotation coverage, this leaves significant gaps in understanding behavior.

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 a single, efficient sentence with zero waste. It's front-loaded with the core action and resources, making it easy to parse quickly without unnecessary details.

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 this is a mutation tool with no annotations and no output schema, the description is incomplete. It doesn't cover behavioral aspects like effects, permissions, or return values, and lacks usage context compared to siblings. For a tool that modifies data in a system with many related tools, more information is needed for effective use.

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 both parameters clearly documented in the schema. The description doesn't add any meaning beyond the schema, such as explaining what 'Record name' entails or providing examples. Baseline 3 is appropriate since the schema does the heavy lifting, but no extra value is added.

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 ('Add') and resources ('existing task to an idea in Assess realm'), making the purpose understandable. However, it doesn't differentiate from sibling tools like 'assess_add_task_to_project' or 'assess_remove_task_from_idea', which would require more specific context about what 'adding' entails in this system.

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. For example, it doesn't explain when to choose this over 'assess_add_task_to_project' or how it relates to 'assess_remove_task_from_idea'. The description lacks context about prerequisites or typical scenarios for usage.

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