Skip to main content
Glama
dragosroua

addTaskManager MCP Server

by dragosroua

assess_create_project

Create a new project in the Assess realm to organize tasks and ideas using the ADD framework, allowing you to define project details and optional start dates.

Instructions

Create a new project in Assess realm.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectNameYesProject name/description (max 1500 chars)
startDateNoOptional start date (ISO format)
collectionRecordNameNoOptional recordName of the parent collection.

Implementation Reference

  • The handler function that implements the tool logic. Creates a mock CloudKit project record in Assess realm (realmId=1), generates recordName and uniqueId using UUID, sets required fields like projectName, timestamps, optional startDate and collection reference, and returns a success message with the new recordName.
    private async createProject(projectName: string, startDateISO?: string, collectionRecordName?: string) {
      const now = Date.now();
      const projectRecordName = `project_ck_${uuidv4()}`;
      const project: ZenTaskticProject = {
        recordType: 'Projects',
        recordName: projectRecordName,
        fields: {
          projectName: { value: projectName },
          realmId: { value: REALM_ASSESS_ID },
          uniqueId: { value: uuidv4() },
          startDate: { value: startDateISO ? new Date(startDateISO).getTime() : now },
          lastModified: { value: now },
          ...(collectionRecordName && { collection: { value: { recordName: collectionRecordName, action: 'NONE' } } }),
        }
      };
      // Mock save: console.log('Mock CloudKit: Creating Project', project);
      return { content: [{ type: 'text', text: `Project "${projectName}" created in Assess realm with ID ${projectRecordName}.` }] };
    }
  • The input schema definition for the 'assess_create_project' tool, specifying properties like projectName (required), optional startDate (ISO datetime), and collectionRecordName.
      name: 'assess_create_project',
      description: 'Create a new project in Assess realm.',
      inputSchema: {
        type: 'object',
        properties: {
          projectName: { type: 'string', description: 'Project name/description (max 1500 chars)' },
          startDate: { type: 'string', format: 'date-time', description: 'Optional start date (ISO format)' },
          collectionRecordName: { type: 'string', description: 'Optional recordName of the parent collection.' }
        },
        required: ['projectName']
      }
    },
  • src/index.ts:666-668 (registration)
    The switch case in the CallToolRequestSchema handler that registers and dispatches to the createProject handler method for the tool name 'assess_create_project'.
      this.validateArgs(args, ['projectName']);
      return await this.createProject(args.projectName, args.startDate, args.collectionRecordName);
    case 'assess_edit_project':
  • Type definition (schema) for ZenTaskticProject used in the handler to structure the CloudKit record fields.
    export interface ZenTaskticProject {
      recordName?: string;
      recordType: 'Projects'; // Note: entity name is 'Projects' in Core Data
      fields: {
        projectName: { value: string }; // Max 1500 chars
        realmId: { value: number }; // Integer 16, default 0
        uniqueId: { value: string }; // UUID
        
        // References (relationships in Core Data)
        context?: { value: CKReference }; // Reference to Contexts record
        collection?: { value: CKReference }; // Reference to Collections record
        realm?: { value: CKReference }; // Reference to Realms record
        tasks?: { value: CKReference[] }; // List of references to Task records
        
        // Dates
        startDate?: { value: number }; // Timestamp
        endDate?: { value: number }; // Timestamp
        lastModified: { value: number }; // Timestamp
        
        // removed description (use projectName), removed isCompleted
      };
    }
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. It states this is a creation operation but doesn't mention permissions required, whether this is a mutating operation (implied but not explicit), what happens on success/failure, or any rate limits. For a creation tool with zero annotation coverage, this is insufficient.

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 that gets straight to the point with no wasted words. It's appropriately sized for a simple creation operation and front-loads the essential information.

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 creation tool with no annotations and no output schema, the description is inadequate. It doesn't explain what a 'project' entails in the Assess realm, what happens after creation, or what the tool returns. Given the complexity of project management systems and the lack of structured metadata, more context is needed.

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, so all parameters are documented in the schema itself. The description doesn't add any additional parameter context beyond what's already in the schema, making the baseline score of 3 appropriate. No parameter-specific guidance is provided in the description text.

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 ('Create') and resource ('new project in Assess realm'), making the purpose immediately understandable. It doesn't differentiate from sibling tools like 'assess_create_collection' or 'assess_create_idea', which would require mentioning what makes a project distinct from those other entities.

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 like 'assess_create_collection' or 'assess_create_idea', nor does it mention prerequisites or context for project creation. It simply states what the tool does without indicating appropriate usage scenarios.

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