Skip to main content
Glama
dragosroua

addTaskManager MCP Server

by dragosroua

get_projects_by_realm

Filter projects in addTaskManager by realm (Assess, Decide, Do) to view tasks based on their current workflow stage.

Instructions

Filter projects by realm.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
realmYesRealm to query (maps to realmId 1, 2, or 3)

Implementation Reference

  • src/index.ts:559-568 (registration)
    Registration of the 'get_projects_by_realm' tool in the MCP server's listTools handler. Defines the tool name, description, and input schema requiring a 'realm' parameter (assess/decide/do).
      name: 'get_projects_by_realm',
      description: 'Filter projects by realm.',
      inputSchema: {
        type: 'object',
        properties: {
          realm: { type: 'string', enum: ['assess', 'decide', 'do'], description: 'Realm to query (maps to realmId 1, 2, or 3)' }
        },
        required: ['realm']
      }
    },
  • Primary handler function that executes the tool logic. Maps realm string to numeric ID and returns a formatted text response with mock project data for the specified realm.
    private async getProjectsByRealm(realm: RealmString) {
      const realmId = realmStringToId(realm);
      const mockProjects = [{ recordName: 'project_456', projectName: 'Sample Project X', realmId }];
      return { content: [{ type: 'text', text: `Projects in ${realm} realm (ID: ${realmId}):\n${mockProjects.map(p => `- ${p.projectName} (${p.recordName})`).join('\n')}` }] };
    }
  • Dispatch handler in CallToolRequestSchema that validates input arguments and invokes the getProjectsByRealm method.
    this.validateArgs(args, ['realm']);
    return await this.getProjectsByRealm(args.realm as RealmString);
  • Supporting helper method in CloudKitService that performs the actual CloudKit database query to retrieve projects filtered by realmId. Used by other tools like get_stalled_items_in_decide.
    async getProjectsByRealm(realmId: number): Promise<ZenTaskticProject[]> {
      return this.queryRecords<ZenTaskticProject>('Projects', {
        filterBy: [{ 
          fieldName: 'realmId', 
          fieldValue: realmId,
          comparator: 'EQUALS' 
        }],
        sortBy: [{ fieldName: 'lastModified', ascending: false }]
      });
    }
  • Type definition for ZenTaskticProject, defining the structure of project records from CloudKit/Core Data, used in query responses.
    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 the full burden of behavioral disclosure. It mentions filtering but doesn't specify whether this is a read-only operation, what permissions are required, how results are returned (e.g., list format, pagination), or any side effects. For a tool with zero annotation coverage, this leaves critical behavioral traits undocumented.

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, front-loading the core action. It's appropriately sized for a simple filtering tool, making it easy to parse without unnecessary elaboration.

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 no annotations, no output schema, and a simple parameter set, the description is incomplete. It doesn't explain what the tool returns (e.g., a list of projects, their properties), behavioral aspects like error handling, or how it fits into the broader context of sibling tools. For a tool with minimal structured data, more descriptive 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, with the 'realm' parameter fully documented via enum and description. The description adds no additional meaning beyond what the schema provides, such as explaining the mapping of realms to realmIds or usage examples. Baseline 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.

Purpose3/5

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

The description 'Filter projects by realm' states the basic action (filter) and resource (projects) with a constraint (by realm), but it's vague about what 'realm' means and doesn't distinguish this tool from sibling tools like 'get_tasks_by_realm' or 'get_ideas' that also retrieve domain objects. It lacks specificity about what kind of filtering or output is provided.

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 'get_ideas' or 'get_tasks_by_realm', nor does it mention prerequisites or context for filtering projects. It implies usage by stating the action but offers no explicit when/when-not instructions or comparisons with sibling tools.

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