Skip to main content
Glama
dragosroua

addTaskManager MCP Server

by dragosroua

assess_create_collection

Create a new collection in the Assess realm to organize tasks, projects, and ideas using the ADD framework for structured task management.

Instructions

Create a new collection in Assess realm.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
collectionNameYesCollection name

Implementation Reference

  • src/index.ts:307-317 (registration)
    Tool registration including name, description, and input schema definition.
    {
      name: 'assess_create_collection',
      description: 'Create a new collection in Assess realm.',
      inputSchema: {
        type: 'object',
        properties: {
          collectionName: { type: 'string', description: 'Collection name' }
        },
        required: ['collectionName']
      }
    },
  • The main handler function that executes the tool. Currently a mock implementation that generates a record name and returns a success message. In production, this would use CloudKitService.saveRecord().
    private async createCollection(collectionName: string) {
      const recordName = `collection_${uuidv4()}`;
      // Mock collection creation via CloudKit
      return { content: [{ type: 'text', text: `Collection "${collectionName}" created with recordName: ${recordName}` }] };
    }
  • TypeScript interface defining the structure of a Collections record for CloudKit, used in create operations.
    interface ZenTaskticCollection {
      recordName?: string;
      recordType: 'Collections';
      fields: {
        collectionName: { value: string }; // Collection name
        uniqueId: { value: string }; // UUID, max 58 chars
        creationDate?: { value: number }; // Timestamp
        lastModified: { value: number }; // Timestamp
        
        // References (relationships in Core Data)
        ideas?: { value: CKReference[] }; // List of references to Ideas records
        projects?: { value: CKReference[] }; // List of references to Projects records
        tasks?: { value: CKReference[] }; // List of references to Task records
      };
    }
  • Dispatch handler in the main tool switch statement that validates arguments and calls the createCollection method.
    case 'assess_create_collection':
      this.validateArgs(args, ['collectionName']);
      return await this.createCollection(args.collectionName);
  • Supporting method in CloudKitService for querying collections, which would be used alongside create operations in a full implementation.
    async getCollections(): Promise<any[]> {
      return this.queryRecords('Collections', {
        sortBy: [{ fieldName: 'collectionName', ascending: true }]
      });
    }
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states this is a creation operation, implying mutation, but doesn't disclose behavioral traits like required permissions, whether collections are unique, what happens on duplicate names, or the response format. For a mutation 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 with zero waste. It's appropriately sized for a simple creation tool and front-loads the key information (action and resource).

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, no output schema, and multiple sibling tools, the description is incomplete. It lacks behavioral context, usage guidance, and details about the result. The agent would need to guess about permissions, error handling, and how this integrates with other Assess tools.

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 description adds no parameter semantics beyond what the input schema provides. With 100% schema description coverage (the schema documents the single parameter 'collectionName' as 'Collection name'), the baseline is 3. The description doesn't elaborate on naming constraints, format, or examples.

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 collection in Assess realm'), making the purpose understandable. However, it doesn't distinguish this tool from other 'create' siblings like assess_create_context, assess_create_idea, assess_create_project, and assess_create_task, which all create different resource types in the same realm.

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, when collections should be created, or how this relates to sibling tools like get_collections (for listing) or assess_archive_project_to_collection (for archiving).

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