Skip to main content
Glama
dragosroua

addTaskManager MCP Server

by dragosroua

get_ideas

Retrieve all ideas stored in the addTaskManager app to support task and project management using the ADD framework.

Instructions

Get all ideas.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Core handler function that executes the tool logic by querying all CloudKit 'Ideas' records sorted by lastModified descending. Called by the MCP server in production mode.
    async getIdeas(): Promise<ZenTaskticIdea[]> {
      return this.queryRecords<ZenTaskticIdea>('Ideas', {
        sortBy: [{ fieldName: 'lastModified', ascending: false }]
      });
    }
  • Top-level MCP tool handler for 'get_ideas'. Dispatches to CloudKitService in production or returns mock data in development, formats the list of ideas as a text response.
    private async getIdeas() {
      return this.withCloudKitOrMock(
        'getIdeas',
        async () => {
          // CloudKit production implementation
          const ideas = await this.cloudKitService.getIdeas();
          
          let response = `All ideas:\n`;
          if (ideas.length === 0) {
            response += 'No ideas found. Time to brainstorm! 💡';
          } else {
            response += ideas.map((idea: any) => {
              const name = idea.fields?.ideaName?.value || 'Unnamed Idea';
              const realmId = idea.fields?.realmId?.value || 1;
              const realmName = realmId === 1 ? 'Assess' : 'Unknown';
              
              return `- ${name} (${idea.recordName}) [${realmName}]`;
            }).join('\n');
          }
          
          return { content: [{ type: 'text', text: response }] };
        },
        async () => {
          // Mock implementation
          const mockIdeas = [{ recordName: 'idea_789', ideaName: 'Brilliant Idea Z' }];
          return { content: [{ type: 'text', text: `Found ${mockIdeas.length} ideas:\n${mockIdeas.map(i => `- ${i.ideaName} (${i.recordName})`).join('\n')}` }] };
        }
      );
    }
  • Tool schema definition including name, description, and empty input schema (no parameters required).
    {
      name: 'get_ideas',
      description: 'Get all ideas.',
      inputSchema: { type: 'object', properties: {} }
    },
  • src/index.ts:746-748 (registration)
    Registration of the tool handler in the CallToolRequestSchema switch statement.
    case 'get_ideas':
      return await this.getIdeas();
    case 'moveToRealm':
  • Type definition for ZenTaskticIdea used by the getIdeas handler for type safety in CloudKit queries.
    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. 'Get all ideas' implies a read operation but lacks details on permissions, rate limits, pagination, or response format. It doesn't specify whether this returns all ideas unconditionally or if there are scoping constraints, leaving significant behavioral gaps.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely concise ('Get all ideas.'), but this brevity borders on under-specification rather than efficient communication. It's front-loaded but lacks necessary elaboration for a tool with no annotations or output schema, failing to earn its place with substantive 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?

Given the complexity of a retrieval tool with no annotations, no output schema, and many sibling tools, the description is incomplete. It doesn't explain what 'ideas' are, how results are returned, or any behavioral traits, making it inadequate for an AI agent to use this tool effectively in context.

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 lack of inputs. The description doesn't add parameter details, which is appropriate here, but it could hint at implicit filters or scoping. Given zero parameters, a baseline of 4 is justified as the description doesn't need to compensate for schema gaps.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Get all ideas' is a tautology that essentially restates the tool name 'get_ideas' without adding meaningful specificity. It doesn't distinguish this tool from its many sibling tools (like 'get_collections', 'get_projects_by_realm', etc.) beyond the resource type, nor does it clarify what 'ideas' represent in this context.

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

Usage Guidelines1/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. With numerous sibling tools for retrieving different resources (e.g., 'get_collections', 'get_projects_by_realm'), there's no indication of context, prerequisites, or exclusions for using 'get_ideas'.

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