TimeTree MCP Server

create_memo

Creates a calendar memo for notes, lists, or checklists that are not scheduled events, and returns its UUID so calendar members can view and update it later.

Instructions

Create a memo in a calendar and return it with its uuid: a note, list, or checklist that is not a scheduled event, such as a shopping list. Other calendar members can see it. Use create_event for something that happens at a time. Change it later with update_memo.

Input Schema

TableJSON Schema

Name	Required	Description
`url`	No	Optional related URL
`date`	No	Optional memo date in YYYY-MM-DD; defaults to today UTC
`note`	No	Memo body text
`title`	Yes	Memo title
`label_id`	No	Color label ID (1-10): 1=Emerald green, 2=Modern cyan, 3=Deep sky blue, 4=Pastel brown, 5=Midnight black, 6=Apple red, 7=French rose, 8=Coral pink, 9=Bright orange, 10=Soft violet
`location`	No	Optional memo location
`checklist`	No	Checklist items for the memo
`calendar_id`	Yes	The calendar ID from list_calendars (numeric string; numbers are also accepted)
`virtual_user_attendees`	No	Virtual member IDs/names related to the memo

Output Schema

TableJSON Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.7.0Oct 22, 2026

changedInput schema / properties / label_id / description

Previous value: -"Color label ID (1-10)"New value: +"Color label ID (1-10): 1=Emerald green, 2=Modern cyan, 3=Deep sky blue, 4=Pastel brown, 5=Midnight black, 6=Apple red, 7=French rose, 8=Coral pink, 9=Bright orange, 10=Soft violet"

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "memo": {
+      "properties": {
+        "calendar_id": {
+          "type": "number"
+        },
+        "checklist": {
+          "type": "array"
+        },
+        "created_at": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "label_color": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "label_id": {
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "location": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "memo_date": {
+          "description": "YYYY-MM-DD",
+          "type": "string"
+        },
+        "note": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "title": {
+          "type": "string"
+        },
+        "updated_at": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "url": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "uuid": {
+          "type": "string"
+        },
+        "virtual_user_attendees": {
+          "type": "array"
+        }
+      },
+      "required": [
+        "uuid",
+        "title",
+        "memo_date"
+      ],
+      "type": "object"
+    },
+    "message": {
+      "type": "string"
+    },
+    "success": {
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "success",
+    "memo"
+  ],
+  "type": "object"
+}

Changed2 schema fields changedv0.4.0Oct 3, 2026

changedInput schema / properties / calendar_id / description

Previous value: -"The calendar ID to create the memo in"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?

Adds real context beyond annotations: the created memo is returned with its uuid, and 'Other calendar members can see it' discloses a visibility side effect that annotations (readOnlyHint=false, destructiveHint=false, openWorldHint=true) do not convey. It stops short of naming required permissions or whether attendee notification occurs, which is the remaining gap.

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?

Three short sentences, front-loaded with the action and its return value, then the definition, then the routing guidance. No filler and nothing buried.

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?

For a creation tool with 9 params, full schema coverage, and an output schema, the description supplies what structured fields cannot: the concept boundary versus events, the visibility consequence, and the follow-up tool. Return-value details are correctly left to the output schema.

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 the schema already explains calendar_id, date defaults, label_id values, and checklist structure. The description's mention of 'note, list, or checklist' loosely maps to the note/checklist fields but adds no syntax or constraint detail beyond the schema. Baseline 3 applies.

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?

States a specific verb and resource ('Create a memo in a calendar') and immediately defines the resource by contrast: 'a note, list, or checklist that is not a scheduled event, such as a shopping list.' That definition is what separates it from create_event, so an agent can pick the right tool without inspecting either 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?

Explicitly routes both alternatives: 'Use create_event for something that happens at a time' and 'Change it later with update_memo.' This covers when to use it, when not to, and which sibling handles the adjacent cases.

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