Skip to main content
Glama

Change, pause or resume a reminder to my human

reminder_update
DestructiveIdempotent

Change one reminder in place; its id, send counts and any field you leave out stay. New text gets reminder_create's checks. Pausing stops its future emails but keeps it. Resuming, or a new repeat or time_zone, starts at the next time after now: missed times are not sent. Resume is refused (reminders_stopped_by_owner) while your owner has reminders stopped. An unknown reminder_id answers reminder_not_found. Returns the reminder; reminder_delete removes it for good.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "status": "paused",
      "instance_id": "orm_exampleexampleexample2",
      "reminder_id": "rem_exampleexampleexample2"
    },
    "name": "reminder_update"
  }
}

Input Schema

NameRequiredDescriptionDefault
textNoNew text, same rules.
repeatNoNew rule: daily or weekly.
statusNopaused: no emails; active: from the next time after now.
time_zoneNoNew IANA time zone, for example Europe/Istanbul. Left out: the current one stays.
instance_idYesUtility instance id from buy or list_utilities.
reminder_idYesreminder id (rem_...) from reminder_create or reminder_list.
passport_tokenNoYour amp_ token, only if you have no app sign-in and cannot send a header.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "instance_id": "orm_exampleexampleexample2",
      +    "reminder_id": "rem_exampleexampleexample2",
      +    "status": "paused"
      +  }
      +]
    • changedInput schema / properties / passport_token / description
      Previous value: -"Your amp_ token, only if your app has no sign-in and cannot send it as an Authorization header."New value: +"Your amp_ token, only if you have no app sign-in and cannot send a header."
  2. Changed4 schema fields changed
    • removedInput schema / $schema
      Removed value: -"https://json-schema.org/draft/2020-12/schema"
    • changedInput schema / properties / passport_token / description
      Previous value: -"Your amp_ token, only if your client cannot send it as an Authorization header; leave it out when your MCP app signed in."New value: +"Your amp_ token, only if your app has no sign-in and cannot send it as an Authorization header."
    • addedInput schema / properties / passport_token / maxLength
      Added value: +200
    • removedInput schema / properties / passport_token / pattern
      Removed value: -"^amp_(?:s_)?[A-Za-z0-9_-]{43}$"
  3. Added

TDQS

A4.6/5.0
Behavior5/5

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

Goes well past the annotations: omitted fields and send counts are preserved, pausing retains the reminder, resuming or changing repeat/time_zone reschedules from the next future time and silently drops missed occurrences, and it names two concrete failure modes (reminders_stopped_by_owner, reminder_not_found). That is exactly the side-effect and precondition detail an agent needs before mutating state.

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?

Roughly five dense sentences, front-loaded with the in-place-edit contract before branching into pause/resume and error cases. The semicolon-heavy packing makes it terse rather than wasteful, though it reads as one long run-on rather than cleanly separated clauses.

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

Completeness5/5

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

For a mutating tool with no output schema, the description covers return value ("Returns the reminder"), preserved state, rescheduling behavior, owner-level blocking, and not-found handling. Nothing an agent needs in order to call it safely is missing.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3, but the description adds real semantics the schema cannot express: a new repeat or time_zone acts as a restart point, missed times are skipped, and text changes inherit reminder_create's validation rules. Only minor detail (e.g. status transitions other than pause/resume) is left implicit.

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?

States a specific verb and resource ("Change one reminder in place") and immediately scopes it against siblings — reminder_create supplies text validation, reminder_delete is the permanent-removal path. An agent can distinguish edit vs create vs delete without opening any schema.

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?

Explicitly routes permanent removal to reminder_delete ("removes it for good") and covers pause vs resume as distinct intents within this tool. It lacks an explicit statement of when NOT to use it (e.g. to create a new reminder, use reminder_create), but the context is unambiguous.

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.