Skip to main content
Glama
nicolascroce

keepsake-mcp

by nicolascroce

snooze_task

Idempotent

Reschedule a task to a new specific date, set it as soon as possible, or mark it as no rush.

Instructions

Reschedule a task to a new date.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesTask UUID
dateYesNew date (YYYY-MM-DD)
date_typeNoNew date type: specific (has a due date, default), asap (do as soon as possible), one_day (someday/no rush)
Behavior3/5

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

Annotations already indicate idempotent and non-destructive behavior. The description adds no extra behavioral context beyond that.

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?

Single sentence, concise and to the point. No unnecessary words, though it could benefit from a bit more detail without being overly long.

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

Completeness4/5

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

For a simple tool with 3 parameters and existing annotations, the description is adequate. It covers the core action. However, it could mention that the tool is idempotent (though annotation covers that).

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%, so the description does not add meaning beyond what the schema already provides. Baseline 3 is appropriate.

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?

The description clearly states the tool reschedules a task to a new date. It uses a specific verb and resource, differentiating it from sibling tools like update_task which may modify other fields.

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 like update_task. The description does not provide context about typical use cases or exclusions.

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/nicolascroce/keepsake-mcp'

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