Skip to main content
Glama
NerdSnipe-Inc

Lofty MCP Server

Official

unfinishCalendar

Reopen a finished calendar item to change its status back to unfinished. Provide a composite calendar ID like '563172-task' or '563172-appointment'.

Instructions

Reopen a finished calendar item (v2 API). Calendar IDs are composite strings like "563172-task" or "563172-appointment".

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
calendarIdYesComposite calendar ID, e.g. "563172-task" or "563172-appointment"
Behavior2/5

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

No annotations are provided, and the description only states the action without revealing any behavioral traits such as side effects, permissions, or idempotency. For a mutation tool, this is insufficient.

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?

Two sentences, no unnecessary words. The first sentence delivers the core purpose, the second provides a valuable example. Very efficient.

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 one parameter and no output schema, the description adequately covers the necessary information. Could optionally mention the return value, but not essential.

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 the description slightly reinforces the parameter format with an example, but does not add significant new meaning beyond the schema description.

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 the action (Reopen) and resource (finished calendar item). Distinguishes from sibling tools like 'finishCalendar' and 'unfinishTaskV2' by specifying 'calendar item' and 'v2 API'.

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 says 'Reopen a finished calendar item', which clearly indicates when to use the tool. However, no exclusions or alternatives are mentioned, but the context is clear given sibling tool names.

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/NerdSnipe-Inc/lofty-mcp'

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