Skip to main content
Glama

Rename Reminder

reminders_rename

Update the title of a specific reminder using its unique identifier. Provide the reminder ID and new title to rename.

Instructions

Rename a reminder by canonical id.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYes
reminder_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior2/5

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

Description minimally indicates mutation ('rename'), but lacks details on side effects, required permissions, or constraints. With no annotations beyond a title, the description does not disclose behavioral traits.

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?

One short sentence with no redundancy. Every word is necessary, though it may be too brief for full clarity.

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?

Given the presence of an output schema, the description could be minimal but still lacks essential usage and behavioral context. For a simple rename, it feels incomplete.

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

Parameters1/5

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

Parameter schemas have 0% description coverage, and the description adds no meaning beyond the parameter names ('reminder_id', 'title'). No explanation of values or constraints.

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?

Description states clear verb 'Rename' and resource 'reminder' with method 'by canonical id'. However, it does not differentiate from sibling tools like 'reminders_update' or 'reminders_rename_list'.

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 on when to use this tool versus alternatives such as 'reminders_update' or 'reminders_rename_list'. No context or exclusions provided.

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/abhinavag-svg/apple-ecosystem-mcp'

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