Skip to main content
Glama

complete_reminder

Idempotent

Mark a reminder as completed or reopen it using its reminder ID; set completed to false to mark it not completed.

Instructions

Mark a reminder as completed, or as not completed with 'completed' set to false.

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": {
      "id": "<id>"
    },
    "name": "complete_reminder"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesReminder id from list_reminders, search_reminders or get_reminder.
completedNotrue to complete (default), false to reopen.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

The annotations already declare idempotentHint=true, destructiveHint=false and readOnlyHint=false, so the safety profile is covered. The description adds the useful detail that passing false reopens rather than deletes, but says nothing about error behavior for missing or already-completed reminders.

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?

A single short sentence with the action front-loaded and no wasted wording. The phrasing 'as not completed with completed set to false' is slightly awkward but remains clear.

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 simple two-parameter mutation with no output schema and annotations that already cover idempotency and safety, the definition is adequate. It leaves minor gaps, such as behavior on an already-completed reminder and its relationship to update_reminder.

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 coverage is 100% and both parameters are fully documented in the schema, including the id source and the completed default. The description only restates the meaning of setting completed to false, adding little beyond the schema, so the baseline 3 holds.

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 and resource ('mark a reminder as completed') and covers both directions, complete and reopen. It does not differentiate itself from the sibling update_reminder, which could plausibly also change completion state.

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

Usage Guidelines3/5

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

The toggle semantics are implied by the description, so an agent can infer that this is the way to complete or reopen a reminder. There is no explicit guidance on when to use this versus update_reminder, and no mention of prerequisites such as a valid reminder id.

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