Skip to main content
Glama
Mnemosyne-OS

Mnemosyne OS

by Mnemosyne-OS
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

mnemosyne_agenda_remove

Destructive

Remove calendar appointments by their exact ids from mnemosyne_agenda_list. Prevents wrong-day deletions by id-only matching; confirm each removed title and start time in the response.

Instructions

Remove appointments from the user's calendar. Read them with mnemosyne_agenda_list first and pass the ids. This tool matches by id only, because "remove my meetings on Thursday" is how an agent removes the wrong Thursday. There is no archive: unlike a To-do task, a removed appointment is gone, so the answer names each one it removed by title and start time for the user to check. A repeating appointment is removed as a whole series, since the calendar cannot cancel a single occurrence. Works with the app closed on a dev install (the headless daemon reads the file); an npm install has no daemon and needs the app running. Scope agenda:write.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
event_idsYesThe appointment ids to remove, exactly as mnemosyne_agenda_list printed them in brackets. Up to 50.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.10.0

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the destructiveHint annotation, the description details real consequences: no archive, removal is permanent, repeating appointments are removed as a whole series, and the response names each removed item. It also discloses environment-dependent daemon behavior, adding significant value.

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?

The description is front-loaded with the core purpose and each sentence carries important caveat or usage information. It is longer than minimal, but every sentence earns its place; no filler.

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

Completeness5/5

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

Despite lacking an output schema, the description explains what the response will name. It covers destructive semantics, repeating events, the id prerequisite, and the daemon/app runtime condition, making it fully actionable for an agent.

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?

The schema already covers the single parameter at 100%. The description adds useful extra semantics: ids must be exactly as mnemosyne_agenda_list printed them in brackets hire up to 50. This goes beyond the schema's generic wording.

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?

The description opens with a specific verb and resource: 'Remove appointments from the user's calendar.' It clearly distinguishes this tool from siblings by emphasizing id-only matching and contrast with archive-able To-do tasks.

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?

It gives explicit procedural guidance: read appointments with mnemosyne_agenda_list first and pass the printed ids. It also warns against phrase-based removal. It does not spell out all exclusions or alternatives, but the context is clear enough for an agent to use it correctly.

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

Deploy Server

Other Tools