Skip to main content
Glama
dragosroua

addTaskManager MCP Server

by dragosroua

assess_create_idea

Capture and assess new ideas within the ADD framework, starting in the Assess realm to evaluate potential before decision-making.

Instructions

Capture a new idea (always starts in Assess realm).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ideaNameYesIdea name/details (max 1500 chars)
collectionRecordNameNoOptional recordName of the parent collection.

Implementation Reference

  • The core handler function `createIdea` that executes the tool logic: constructs a ZenTaskticIdea record with Assess realmId=1, generates UUIDs, sets timestamps and optional collection reference, and returns a mock success response (in production would save to CloudKit).
    private async createIdea(ideaName: string, collectionRecordName?: string) {
      const now = Date.now();
      const ideaRecordName = `idea_ck_${uuidv4()}`;
      const idea: ZenTaskticIdea = {
        recordType: 'Ideas',
        recordName: ideaRecordName,
        fields: {
          ideaName: { value: ideaName },
          realmId: { value: REALM_ASSESS_ID }, // Ideas always start in Assess
          uniqueId: { value: uuidv4() },
          lastModified: { value: now },
          ...(collectionRecordName && { collection: { value: { recordName: collectionRecordName, action: 'NONE' } } }),
        }
      };
      // Mock save: console.log('Mock CloudKit: Creating Idea', idea);
      return { content: [{ type: 'text', text: `Idea "${ideaName}" captured in Assess realm with ID ${ideaRecordName}.` }] };
    }
  • Input schema definition for the assess_create_idea tool, specifying required 'ideaName' string and optional 'collectionRecordName'.
    name: 'assess_create_idea',
    description: 'Capture a new idea (always starts in Assess realm).',
    inputSchema: {
      type: 'object',
      properties: {
        ideaName: { type: 'string', description: 'Idea name/details (max 1500 chars)' },
        collectionRecordName: { type: 'string', description: 'Optional recordName of the parent collection.' }
      },
      required: ['ideaName']
    }
  • src/index.ts:672-674 (registration)
    Tool registration in the CallToolRequestSchema switch statement: validates args and delegates to createIdea handler.
      this.validateArgs(args, ['ideaName']);
      return await this.createIdea(args.ideaName, args.collectionRecordName);
    case 'assess_edit_idea':
  • TypeScript interface defining the structure of Idea records for CloudKit/Core Data compatibility, used in the handler.
    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
      };
    }
  • src/index.ts:296-306 (registration)
    Tool registration entry in the ListToolsRequestSchema response array, exposing the tool with name, description, and schema.
      name: 'assess_create_idea',
      description: 'Capture a new idea (always starts in Assess realm).',
      inputSchema: {
        type: 'object',
        properties: {
          ideaName: { type: 'string', description: 'Idea name/details (max 1500 chars)' },
          collectionRecordName: { type: 'string', description: 'Optional recordName of the parent collection.' }
        },
        required: ['ideaName']
      }
    },
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool creates a new idea and specifies it 'always starts in Assess realm', which adds some workflow context. However, it lacks critical details such as permissions required, whether the creation is reversible, what happens to the idea after creation, 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 front-loads the core action ('Capture a new idea') and adds contextual detail ('always starts in Assess realm') without unnecessary elaboration. Every word serves a purpose, making it highly concise and well-structured.

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 incomplete. It lacks details on behavioral aspects like permissions, reversibility, or response format, and doesn't fully guide usage relative to siblings. While concise, it doesn't compensate for the missing structured data, leaving gaps in understanding how to effectively use the tool.

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, with clear documentation for both parameters ('ideaName' and 'collectionRecordName'). The description doesn't add any parameter-specific details beyond what's in the schema, such as examples or formatting nuances. Given the high schema coverage, a baseline score of 3 is appropriate as the schema does the heavy lifting.

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 verb ('Capture') and resource ('a new idea'), making the purpose immediately understandable. It distinguishes this tool from siblings like 'assess_edit_idea' by specifying creation vs. editing, though it doesn't explicitly differentiate from other 'create' tools like 'assess_create_project' or 'assess_create_task' beyond mentioning the 'Assess realm' context.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage context with '(always starts in Assess realm)', suggesting this tool is for initial idea creation in a specific workflow stage. However, it doesn't provide explicit guidance on when to use this versus alternatives like 'assess_create_project' or 'assess_edit_idea', nor does it mention prerequisites or exclusions.

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