Skip to main content
Glama

complete_reminder

Complete a reminder by providing its ID or title. Optionally specify the list name to narrow the search.

Instructions

Mark an exact or uniquely matching reminder as complete.

Args: identifier: Reminder id or name/title text list_name: Optional Reminders list name

Returns: Structured JSON with the updated reminder or an error message.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
list_nameNo
identifierYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior2/5

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

No annotations provided, so description must cover behavior. Does not disclose side effects, uniqueness handling, or error conditions beyond 'error message'.

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?

Concise, structured with Args and Returns sections. No wasted 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?

Output schema exists but not detailed; description summarizes return. Lacks clarity on uniqueness constraints and error scenarios. Adequate but incomplete.

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?

With 0% schema coverage, description adds meaning: identifier can be id or text, list_name narrows search. Lacks details on case sensitivity or id format.

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?

Clearly states action ('Mark as complete') on resource ('reminder') with specificity ('exact or uniquely matching'). Distinguishes from siblings like delete_reminder and update_reminder.

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?

Provides parameter usage hints ('id or name/title text', 'optional list name') but lacks guidance on when to use this tool over update_reminder or other alternatives.

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/altic-dev/altic-mcp'

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