Skip to main content
Glama

Create reminder

create_reminder

Create a reminder for the guide, optionally linked to an activity or booking.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "title": "<title>",
      "schedule_kind": "<schedule_kind>"
    },
    "name": "create_reminder"
  }
}

Input Schema

NameRequiredDescriptionDefault
noteNo
titleYes
remind_onNoThe date for a one-off reminder.
booking_idNo
notify_smsNo
start_dateNoThe first date for a daily reminder.
activity_idNo
business_idNoThe id of the business to act on, from list_businesses. Optional when this connection covers a single business.
remind_timeNoLocal reminder time in HH:MM format.
notify_emailNo
schedule_kindYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=false, so the safety profile is covered structurally. However, the description says nothing about what actually happens on creation: whether notify_sms/notify_email trigger messages immediately or at remind_time, how the once/daily schedule drives which dates are used, or whether reminders are per-guide or per-business. For an 11-parameter mutation tool these are real gaps, so the description adds little beyond annotations.

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?

One front-loaded sentence with no wasted words; the core verb and resource come first and the optional linkage follows. It is efficient, though its brevity is part of why parameters go unexplained.

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 no-output-schema mutation tool with 11 parameters, a conditional scheduling model, and only 36% schema coverage, a single sentence is thin. It is not misleading, but an agent still lacks enough to correctly choose schedule_kind and its dependent date fields or to anticipate notification side effects.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 36%, so the description carries more of the burden than usual, yet it only touches the two linking IDs (activity/booking) by implication. It never explains the critical schedule_kind enum ('once' vs 'daily') and its dependency on remind_on vs start_date, nor the notification flags, remind_time format, or business_id scoping.

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?

States a specific verb (create) plus resource (reminder), scoped to the guide, and notes the optional activity/booking linkage. An agent can distinguish it from update_reminder/delete_reminder/complete_reminder by the verb alone, though the description never explicitly names those siblings or their boundary.

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 phrase 'optionally linked to an activity or booking' hints at one usage context but gives no explicit when-to-use versus update_reminder or complete_reminder, no prerequisites, and no statement of when not to call it.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources