TimeTree MCP Server

list_memos

Read-only

Retrieve calendar memos—notes, lists, and checklists that are not scheduled events—optionally filtered by last update time and limited in count.

Instructions

List the memos in a calendar: notes, lists, and checklists that are not scheduled events. Use get_events for events (it also includes memos unless include_memos is false). Optionally only memos updated after a time.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "calendar_id": "<calendar_id>"
    },
    "name": "list_memos"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Optional limit on number of memos returned
`calendar_id`	Yes	The calendar ID from list_calendars (numeric string; numbers are also accepted)
`updated_after`	No	Only return memos updated after this Unix timestamp in milliseconds

Output Schema

Name	Required	Description	Default
`memos`	Yes
`total`	Yes
`calendar_id`	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": {
+    "calendar_id": {
+      "type": "number"
+    },
+    "memos": {
+      "items": {
+        "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"
+      },
+      "type": "array"
+    },
+    "total": {
+      "type": "number"
+    }
+  },
+  "required": [
+    "calendar_id",
+    "memos",
+    "total"
+  ],
+  "type": "object"
+}

Changed2 schema fields changedv0.4.0Oct 3, 2026

changedInput schema / properties / calendar_id / description

Previous value: -"The calendar ID to list memos from"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.2/5.0

Behavior4/5

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

Annotations already cover the read-only and open-world profile, so the description's job is lighter. It adds real value by disclosing the content scope (memos exclude scheduled events) and the overlap/duplication behavior with get_events, which an agent could not infer from annotations. It says nothing about ordering or pagination, but an output schema exists to cover returns.

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?

Three tight sentences, front-loaded with the core purpose and followed by the sibling routing hint and the optional filter. No wasted clauses, though the trailing "Optionally only memos updated after a time" is slightly awkwardly phrased compared to the rest.

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 simple three-parameter read tool with full schema coverage, annotations, and an output schema, nothing an agent needs in order to call it correctly is missing. Purpose, scope, sibling routing, and the optional filter are all present.

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 all three parameters are already documented in the schema, including that calendar_id comes from list_calendars and that updated_after is a Unix millisecond timestamp. The description only echoes the updated_after filter in prose without adding format or default semantics, which is the baseline 3 case.

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?

Specific verb and resource ("List the memos in a calendar") plus a definition of what a memo is — notes, lists, checklists that are not scheduled events. It explicitly contrasts itself with the sibling get_events, so an agent can distinguish the two without opening 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 Guidelines4/5

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

It names the alternative (get_events) and the condition selecting it (events, not memos), and notes that get_events also returns memos unless include_memos is false — helpful routing context. It stops short of an explicit "use this tool when you want only memos without event payload", leaving that inference to the agent.

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