Skip to main content
Glama
dragosroua

addTaskManager MCP Server

by dragosroua

get_collections

Retrieve all collections from the addTaskManager MCP Server to manage tasks, projects, and ideas using the ADD framework across Assess, Decide, and Do realms.

Instructions

Get all collections.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/index.ts:587-591 (registration)
    Tool registration including name, description, and input schema (empty object)
    {
      name: 'get_collections',
      description: 'Get all collections.',
      inputSchema: { type: 'object', properties: {} }
    },
  • Primary MCP tool handler for 'get_collections'. Dispatches to CloudKitService in production mode or returns mock data in development. Formats results as text response.
    private async getCollections() {
      return this.withCloudKitOrMock(
        'getCollections',
        async () => {
          // CloudKit production implementation
          const collections = await this.cloudKitService.getCollections();
          
          let response = `All collections:\n`;
          if (collections.length === 0) {
            response += 'No collections found. Create some to organize your tasks! 📋';
          } else {
            response += collections.map((collection: any) => {
              const name = collection.fields?.collectionName?.value || 'Unnamed Collection';
              
              return `- ${name} (${collection.recordName})`;
            }).join('\n');
          }
          
          return { content: [{ type: 'text', text: response }] };
        },
        async () => {
          // Mock implementation
          const mockCollections = [
            { recordName: 'collection_1', collectionName: 'Work Projects' },
            { recordName: 'collection_2', collectionName: 'Personal Goals' },
            { recordName: 'collection_3', collectionName: 'Done' }
          ];
          return { content: [{ type: 'text', text: `All collections:\n${mockCollections.map(c => `- ${c.collectionName} (${c.recordName})`).join('\n')}` }] };
        }
      );
    }
  • Dispatch from MCP CallToolRequestSchema switch statement to the getCollections handler method
      return await this.getCollections();
    case 'get_tasks_by_context':
  • CloudKitService helper method queried by MCP handler. Performs sorted query on 'Collections' record type.
    async getCollections(): Promise<any[]> {
      return this.queryRecords('Collections', {
        sortBy: [{ fieldName: 'collectionName', ascending: true }]
      });
    }
  • TypeScript interface defining the structure of Collection records from CloudKit/CoreData model.
    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
      };
    }
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. 'Get all collections' implies a read-only operation, but it doesn't specify whether this requires authentication, how data is returned (e.g., format, pagination), or any rate limits. For a tool with zero annotation coverage, this lack of detail is a significant gap in transparency.

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 'Get all collections' is a single, efficient sentence that front-loads the core purpose without any wasted words. It's appropriately sized for a simple retrieval tool, making it easy for an agent to parse quickly.

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 lack of annotations and output schema, the description is incomplete for effective tool use. It doesn't explain what 'collections' are, how results are structured, or any behavioral constraints. For a tool in a complex server with many siblings, more context is needed to ensure the agent can invoke it correctly and interpret outputs.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 0 parameters with 100% description coverage, so the schema fully documents the absence of inputs. The description adds no parameter information, which is appropriate since there are no parameters to describe. This meets the baseline of 4 for tools with zero parameters, as no additional semantic value is needed beyond the schema.

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 'Get all collections' clearly states the verb ('Get') and resource ('collections'), making the purpose immediately understandable. It distinguishes this from sibling tools that perform assessments, authentication, decisions, or operations on other resources like ideas, projects, and tasks. However, it doesn't specify what 'collections' contain or their scope, which keeps it from being fully specific.

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 any prerequisites, such as authentication, or differentiate it from similar tools like 'assess_create_collection' or 'assess_archive_project_to_collection'. Without context, an agent might struggle to choose this tool appropriately among the many sibling tools listed.

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