Skip to main content
Glama
byndcloud

Unofficial Dex CRM MCP Server

by byndcloud

dex_delete_reminder

Permanently delete a reminder from your CRM. For recurring reminders, this action stops all future occurrences by removing the specified reminder ID.

Instructions

Permanently delete a reminder. For recurring reminders, this stops all future occurrences.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
reminderIdYes

Implementation Reference

  • Handler implementation for the dex_delete_reminder tool.
    server.tool(
      "dex_delete_reminder",
      "Permanently delete a reminder. For recurring reminders, this stops all future occurrences.",
      { reminderId: z.string() },
      async (args) => {
        try {
          const result = await dex.delete(`/v1/reminders/${args.reminderId}`);
          return toResult(result);
        } catch (error) {
          return toError(error);
        }
      }
    );
  • Registration of reminder tools, including dex_delete_reminder, within the registerReminderTools function.
    export function registerReminderTools(server: McpServer): void {
      server.tool(
        "dex_create_reminder",
        "Create a new reminder, optionally linked to contacts. Supports recurrence (e.g. 'weekly', 'monthly').",
        {
          text: z.string().describe("Reminder text / title"),
          dueDate: z.string().describe("Due date — accepts 'YYYY-MM-DD' or full ISO 8601 datetime (e.g. '2025-12-31' or '2025-12-31T10:00:00Z')"),
          dueTime: z.string().optional().describe("Optional due time as ISO 8601 datetime (e.g. '2025-12-31T14:00:00Z')"),
          contactIds: z.array(z.string()).optional().describe("Optional list of contact IDs to link to this reminder"),
          recurrence: z.string().optional().describe("Recurrence pattern (e.g. 'weekly', 'monthly')"),
          isComplete: z.boolean().optional(),
        },
        async (args) => {
          try {
            const result = await dex.post("/v1/reminders/", {
              reminder: toReminderBody(args),
            });
            return toResult(result);
          } catch (error) {
            return toError(error);
          }
        }
      );
    
      server.tool(
        "dex_update_reminder",
        "Update a reminder by ID. Modify text, due date/time, linked contacts, recurrence, completion status, and notification flags.",
        {
          reminderId: z.string(),
          reminder: z.object({
            text: z.string().optional().describe("Reminder text / title"),
            dueDate: z.string().optional().describe("Due date — accepts 'YYYY-MM-DD' or full ISO 8601 datetime"),
            dueTime: z.string().optional().describe("Optional due time as ISO 8601 datetime"),
            contactIds: z.array(z.string()).optional().describe("List of contact IDs to link to this reminder"),
            recurrence: z.string().optional().describe("Recurrence pattern (e.g. 'weekly', 'monthly')"),
            isComplete: z.boolean().optional(),
            lastCompletedAt: z.string().optional().describe("ISO 8601 datetime of last completion"),
            nextOccurrenceAt: z.string().optional().describe("ISO 8601 datetime of next occurrence"),
            emailSent: z.boolean().optional(),
            pushNotificationSent: z.boolean().optional(),
          }),
        },
        async (args) => {
          try {
            const { lastCompletedAt, nextOccurrenceAt, emailSent, pushNotificationSent, ...base } = args.reminder;
            const result = await dex.put(`/v1/reminders/${args.reminderId}`, {
              reminder: {
                ...toReminderBody(base),
                ...(lastCompletedAt !== undefined && { last_completed_at: toDateTime(lastCompletedAt) }),
                ...(nextOccurrenceAt !== undefined && { next_occurrence_at: toDateTime(nextOccurrenceAt) }),
                ...(emailSent !== undefined && { email_sent: emailSent }),
                ...(pushNotificationSent !== undefined && { push_notification_sent: pushNotificationSent }),
              },
            });
            return toResult(result);
          } catch (error) {
            return toError(error);
          }
        }
      );
    
      server.tool(
        "dex_delete_reminder",
        "Permanently delete a reminder. For recurring reminders, this stops all future occurrences.",
        { reminderId: z.string() },
        async (args) => {
          try {
            const result = await dex.delete(`/v1/reminders/${args.reminderId}`);
            return toResult(result);
          } catch (error) {
            return toError(error);
          }
        }
      );
    }
Behavior3/5

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

With no annotations provided, the description carries the full burden. It discloses key behavioral traits: the deletion is permanent, and for recurring reminders it stops all future occurrences. However, it doesn't mention permission requirements, error conditions, or what happens to associated data, leaving some gaps for a destructive operation.

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 perfectly concise with two sentences that each earn their place: the first states the core action, the second addresses an important edge case. It's front-loaded with the primary purpose and wastes no words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive tool with no annotations and no output schema, the description provides adequate but incomplete context. It covers the permanence and recurring reminder behavior well, but lacks information about permissions, error handling, and what the tool returns. Given the complexity of a delete operation, more completeness would be beneficial.

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 0%, so the description must compensate. It doesn't explicitly mention the 'reminderId' parameter or provide any details about its format or where to obtain it. The description adds no parameter-specific information beyond what's implied by the tool name.

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

Purpose5/5

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

The description clearly states the specific action ('permanently delete') and resource ('a reminder'), and distinguishes itself from siblings by addressing the special case of recurring reminders. It goes beyond a simple tautology by explaining the effect on recurring occurrences.

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

Usage Guidelines4/5

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

The description provides clear context about when to use this tool (to delete reminders, including handling recurring ones), but it doesn't explicitly mention when not to use it or name specific alternatives. However, the sibling list includes 'dex_update_reminder' as a potential alternative for modifying rather than deleting.

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/byndcloud/unofficial-dex-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server