Skip to main content
Glama
dragosroua

addTaskManager MCP Server

by dragosroua

decide_set_task_alert

Set alerts for tasks in the Decide realm to receive notifications at specified times, helping users manage deadlines and follow-ups within the ADD framework.

Instructions

Set task alerts in Decide realm.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
taskRecordNameYesTask record name
alertDateTimeYesAlert date and time in ISO format for localNotification

Implementation Reference

  • src/index.ts:466-476 (registration)
    Registration of the 'decide_set_task_alert' tool in the MCP server's listTools handler, including name, description, and input schema definition.
      name: 'decide_set_task_alert',
      description: 'Set task alerts in Decide realm.',
      inputSchema: {
        type: 'object',
        properties: {
          taskRecordName: { type: 'string', description: 'Task record name' },
          alertDateTime: { type: 'string', format: 'date-time', description: 'Alert date and time in ISO format for localNotification' }
        },
        required: ['taskRecordName', 'alertDateTime']
      }
    },
  • Dispatch handler in CallToolRequestSchema that validates arguments and invokes the setTaskAlert method for the tool.
    case 'decide_set_task_alert':
      this.validateArgs(args, ['taskRecordName', 'alertDateTime']);
      return await this.setTaskAlert(args.taskRecordName, args.alertDateTime);
  • Tool handler method that forwards the call to the core setAlertForTask implementation.
    private async setTaskAlert(taskRecordName: string, alertDateTime: string) {
      return this.setAlertForTask(taskRecordName, alertDateTime);
    }
  • Core tool execution logic (mock implementation) that simulates setting the task's localNotification field with the alert datetime.
    private async setAlertForTask(taskRecordName: string, alertDateTimeISO: string) {
      // Mock fetch & check realm (should be REALM_DECIDE_ID)
      // Mock update: console.log('Mock CloudKit: Setting localNotification', alertDateTimeISO, 'for Task', taskRecordName);
      return { content: [{ type: 'text', text: `Alert at ${alertDateTimeISO} set for Task ${taskRecordName} in Decide realm.` }] };
    }
  • Type definition in ZenTaskticTask interface for the localNotification field used to store task alerts.
    localNotification?: { value: string }; // Alert date/trigger (max 100 chars)
Behavior2/5

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

No annotations are provided, so the description carries full burden. It implies a write operation ('Set') but doesn't disclose behavioral traits like whether this requires authentication, if alerts are reversible, what happens on invalid inputs, or rate limits. The description adds minimal context beyond the basic action, leaving key behaviors unspecified.

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

Conciseness4/5

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

The description is a single, efficient sentence with no wasted words. It's front-loaded with the core action, though it could be slightly more informative without losing conciseness. Overall, it's appropriately sized for a simple tool.

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 and no output schema, the description is incomplete. It lacks details on what the tool returns (e.g., success confirmation, error messages) and behavioral aspects like side effects or error handling. For a mutation tool with two required parameters, more context is needed to guide effective use.

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%, with clear parameter descriptions in the schema. The description doesn't add any meaning beyond the schema (e.g., it doesn't explain 'taskRecordName' format or 'alertDateTime' implications). Baseline 3 is appropriate since the schema adequately documents parameters, but no extra value is provided.

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 states the action ('Set task alerts') and domain ('Decide realm'), which clarifies the basic purpose. However, it's vague about what 'alerts' entail (e.g., notifications, reminders) and doesn't distinguish this from sibling tools like 'decide_set_task_due_date' or 'decide_set_project_interval', which also involve task/project settings in the same realm.

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?

No guidance is provided on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., task must exist), exclusions, or compare to related tools such as 'decide_set_task_due_date' (which might handle due dates without alerts) or general task management tools in the sibling list.

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