Skip to main content
Glama
dragosroua

addTaskManager MCP Server

by dragosroua

decide_set_project_interval

Define project timelines by setting start and end dates for tasks within the Decide realm of the addTaskManager system.

Instructions

Set project interval (start date and end date) in Decide realm.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectRecordNameYesRecord name of the project
startDateYesStart date in ISO format
endDateYesEnd date in ISO format

Implementation Reference

  • src/index.ts:441-452 (registration)
    Tool registration in the ListTools response array, defining name, description, and input schema.
      name: 'decide_set_project_interval',
      description: 'Set project interval (start date and end date) in Decide realm.',
      inputSchema: {
        type: 'object',
        properties: {
          projectRecordName: { type: 'string', description: 'Record name of the project' },
          startDate: { type: 'string', format: 'date-time', description: 'Start date in ISO format' },
          endDate: { type: 'string', format: 'date-time', description: 'End date in ISO format' }
        },
        required: ['projectRecordName', 'startDate', 'endDate']
      }
    },
  • Handler dispatch in the CallToolRequestHandler switch statement, with argument validation.
    case 'decide_set_project_interval':
      this.validateArgs(args, ['projectRecordName', 'startDate', 'endDate']);
      return await this.setProjectInterval(args.projectRecordName, args.startDate, args.endDate);
  • Primary handler method for the tool. Delegates to setDueDateForItem to update project endDate (note: startDate parameter is validated but unused in mock implementation).
    private async setProjectInterval(projectRecordName: string, startDate: string, endDate: string) {
      return this.setDueDateForItem(projectRecordName, 'Project', endDate);
    }
  • Supporting helper method that provides the mock implementation for setting endDate on Decide realm items (tasks or projects).
    private async setDueDateForItem(itemRecordName: string, itemType: 'Task' | 'Project', endDateISO: string) {
      // Mock fetch & check realm (should be REALM_DECIDE_ID)
      const endDateTimestamp = new Date(endDateISO).getTime();
      // Mock update: console.log('Mock CloudKit: Setting endDate', endDateTimestamp, 'for', itemType, itemRecordName);
      return { content: [{ type: 'text', text: `Due date (endDate) ${endDateISO} set for ${itemType} ${itemRecordName} in Decide realm.` }] };
    }
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states this is a 'Set' operation (implying mutation) but doesn't describe what happens on success/failure, whether changes are reversible, permission requirements, or side effects. For a mutation tool with zero annotation coverage, this leaves critical behavioral aspects unspecified.

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 wasted words. It's appropriately sized for a simple setter tool and front-loads the essential information. Every word earns its place.

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 mutation tool with no annotations and no output schema, the description is incomplete. It doesn't explain what the tool returns, error conditions, or behavioral implications. While the schema covers parameters well, the overall context for safe and effective use is insufficient given the tool's complexity as a write operation.

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?

Schema description coverage is 100%, so the schema already fully documents all three parameters (projectRecordName, startDate, endDate). The description adds no additional parameter semantics beyond what's in the schema, such as format examples or constraints. Baseline 3 is appropriate when 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 action ('Set project interval') and specifies the resource ('project') and scope ('in Decide realm'). It distinguishes this tool from siblings like 'decide_set_task_due_date' by focusing on projects rather than tasks, but doesn't explicitly contrast with other project-related tools like 'assess_edit_project'.

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 (e.g., project must exist), when not to use it, or how it differs from similar tools like 'assess_edit_project' which might also modify project dates. The context 'in Decide realm' is helpful but insufficient for usage decisions.

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