TimeTree MCP Server

add_event_comment

Post a comment on a TimeTree calendar event and return its comment ID. Comments are visible to everyone in the calendar and send no push notification by default.

Instructions

Post a comment on an event and return it with its id. Comments are visible to everyone in the calendar; by default no push notification is sent (silent). Get event_uuid from get_events. To change the event's own note use update_event; to edit or remove a comment later use update_event_comment or delete_event_comment.

Input Schema

TableJSON Schema

Name	Required	Description
`silent`	No	Whether to avoid push notifications when supported (default: true)
`content`	Yes	Comment content
`event_uuid`	Yes	The event UUID to comment on
`calendar_id`	Yes	The calendar ID from list_calendars (numeric string; numbers are also accepted)

Output Schema

TableJSON Schema

Name	Required	Description	Default
`comment`	Yes
`message`	No
`success`	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": {
+    "comment": {
+      "properties": {
+        "author_id": {
+          "description": "User ID of the author",
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "author_type": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "calendar_id": {
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "content": {
+          "type": "string"
+        },
+        "created_at": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "editor_id": {
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "event_id": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "id": {
+          "description": "comment_id for update_event_comment and delete_event_comment",
+          "type": "string"
+        },
+        "images": {
+          "items": {
+            "properties": {
+              "filename": {
+                "type": [
+                  "string",
+                  "null"
+                ]
+              },
+              "height": {
+                "type": [
+                  "number",
+                  "string",
+                  "null"
+                ]
+              },
+              "image_index": {
+                "minimum": 0,
+                "type": "integer"
+              },
+              "width": {
+                "type": [
+                  "number",
+                  "string",
+                  "null"
+                ]
+              }
+            },
+            "required": [
+              "image_index",
+              "filename",
+              "width",
+              "height"
+            ],
+            "type": "object"
+          },
+          "type": "array"
+        },
+        "updated_at": {
+          "type": [
+            "string",
+            "null"
+          ]
+        }
+      },
+      "required": [
+        "id",
+        "content",
+        "images"
+      ],
+      "type": "object"
+    },
+    "message": {
+      "type": "string"
+    },
+    "success": {
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "success",
+    "comment"
+  ],
+  "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.7/5.0

Behavior4/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false, idempotentHint=false), the description discloses audience ("comments are visible to everyone in the calendar") and notification behavior (default silent, no push). It would be stronger if it warned about duplicate posting given idempotentHint=false, or mentioned any rate/permission limits.

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 return value, then side effects, then sibling routing. No filler and no repetition.

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?

Output schema exists so return details need not be spelled out, and all four parameters are schema-documented. The description covers action, side effect, identifier sourcing, and alternatives — everything an agent needs to invoke it correctly.

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?

Schema coverage is 100%, so baseline is 3; the description still adds value by telling the agent where event_uuid comes from (get_events) and reinforcing the silent-no-notification default. calendar_id and content semantics are left to the schema.

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 ("Post a comment on an event") plus the return shape ("return it with its id"). It also explicitly names the sibling tools it is not (update_event, update_event_comment, delete_event_comment), so an agent can disambiguate without opening schemas.

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?

Gives explicit routing: use get_events to obtain event_uuid, use update_event for the event's own note, and use update_event_comment/delete_event_comment for later edits or removal. When-to-use and when-to-use-something-else are both covered.

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