TimeTree MCP Server

delete_memo

DestructiveIdempotent

Permanently delete a memo by its UUID; use list_memos to find the memo_uuid. This action cannot be undone and does not apply to regular events (use delete_event instead).

Instructions

Delete a memo. Cannot be undone. Get memo_uuid from list_memos. Fails for regular events (use delete_event).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`memo_uuid`	Yes	The memo UUID (same as event UUID)
`calendar_id`	Yes	The calendar ID from list_calendars (numeric string; numbers are also accepted)

Output Schema

TableJSON Schema

Name	Required	Description	Default
`message`	No
`success`	Yes
`deleted_memo_uuid`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.7.0Oct 22, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "deleted_memo_uuid": {
+      "type": "string"
+    },
+    "message": {
+      "type": "string"
+    },
+    "success": {
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "success",
+    "deleted_memo_uuid"
+  ],
+  "type": "object"
+}

Changed2 schema fields changedv0.4.0Oct 3, 2026

changedInput schema / properties / calendar_id / description

Previous value: -"The calendar ID"New value: +"The calendar ID from list_calendars (numeric string; numbers are also accepted)"

changedInput schema / properties / calendar_id / type
```
Previous value: -"number"New value: +"string"
```

First observedv0.3.0May 27, 2026

TDQS

A4.5/5.0

Behavior4/5

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

The annotations already declare destructiveHint=true, idempotentHint=true, and openWorldHint=true. The description reinforces permanence with 'Cannot be undone' and adds a useful behavioral boundary by noting the tool fails for regular events. It does not cover permissions or error details, but the failure-mode guidance is valuable context beyond the annotations.

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?

Four short sentences, each earning its place: operation, irreversibility, UUID source, and failure boundary. The core action and constraints are front-loaded with no wasted prose.

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?

Given the rich annotations, full schema descriptions, and presence of an output schema, the description supplies everything an agent needs: what is deleted, that it is permanent, where to get the memo UUID, and when to choose delete_event instead. No material invocation detail is missing.

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 description coverage is 100%, so both calendar_id and memo_uuid are already documented in the input schema. The description adds only a sourcing hint for memo_uuid ('from list_memos'); it does not elaborate on the calendar_id parameter beyond what the schema already states. Baseline 3 is appropriate when the schema carries the parameter documentation.

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: 'Delete a memo.' It then explicitly distinguishes this tool from delete_event by warning that it 'Fails for regular events (use delete_event).' An agent can identify the exact operation and sibling boundary without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It tells the agent where to source the required UUID ('Get memo_uuid from list_memos') and names the competing alternative for regular events ('use delete_event'). This is explicit when-to-use and when-not-to-use guidance, not merely implied context.

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