Skip to main content
Glama
byndcloud

Unofficial Dex CRM MCP Server

by byndcloud
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

dex_create_reminder

Create reminders with due dates, optional recurrence patterns, and contact linking to manage tasks in your Dex CRM system.

Instructions

Create a new reminder, optionally linked to contacts. Supports recurrence (e.g. 'weekly', 'monthly').

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
textYesReminder text / title
dueDateYesDue date — accepts 'YYYY-MM-DD' or full ISO 8601 datetime (e.g. '2025-12-31' or '2025-12-31T10:00:00Z')
dueTimeNoOptional due time as ISO 8601 datetime (e.g. '2025-12-31T14:00:00Z')
contactIdsNoOptional list of contact IDs to link to this reminder
recurrenceNoRecurrence pattern (e.g. 'weekly', 'monthly')
isCompleteNo

Implementation Reference

  • src/tools/reminders.ts:58-67 (handler)
    The handler function for dex_create_reminder that sends a POST request to the Dex API.
    async (args) => {
  try {
    const result = await dex.post("/v1/reminders/", {
      reminder: toReminderBody(args),
    });
    return toResult(result);
  } catch (error) {
    return toError(error);
  }
}
  • src/tools/reminders.ts:50-57 (schema)
    Zod schema defining the input parameters for dex_create_reminder.
    {
  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(),
},
  • src/tools/reminders.ts:47-57 (registration)
    Tool registration for dex_create_reminder using the MCP server instance.
    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(),
  },

Tool Definition Quality

C2.9/5.0
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 optional features (contact linking, recurrence) but fails to address critical aspects like required permissions, whether the operation is idempotent, error conditions, or what the response contains. For a creation tool with mutation implications, this leaves significant gaps.

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 that front-loads the core purpose and highlights key optional features without redundancy. Every word earns its place, making it easy to parse quickly.

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 creation tool with no annotations and no output schema, the description is incomplete. It lacks information on behavioral traits (e.g., side effects, error handling), response format, and detailed usage context, which are essential for an agent to invoke it correctly in a broader workflow.

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 high (83%), so the baseline is 3. The description adds minimal value beyond the schema by mentioning contact linking and recurrence examples, but it doesn't explain parameter interactions (e.g., how dueDate and dueTime relate) or provide additional context for parameters like isComplete.

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 ('Create a new reminder') and mentions optional features ('linked to contacts', 'recurrence'), which distinguishes it from other creation tools like dex_create_contact or dex_create_note. However, it doesn't explicitly differentiate from dex_update_reminder, which might handle similar fields.

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, when not to use it, or how it differs from sibling tools like dex_update_reminder or dex_delete_reminder, leaving the agent to infer usage from context alone.

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