TimeTree MCP Server

get_calendar_labels

Read-only

List a calendar's 10 color labels with IDs, names, colors, and order so you can use the IDs to create or filter events.

Instructions

List the 10 color labels of a calendar with their IDs, names, colors, and order. Use the IDs as label_id when creating or filtering events; rename or recolor them with update_calendar_labels.

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": "get_calendar_labels"
  }
}

Input Schema

Name	Required	Description	Default
`calendar_id`	Yes	The calendar ID from list_calendars (numeric string; numbers are also accepted)

Output Schema

Name	Required	Description	Default
`total`	Yes
`labels`	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"
+    },
+    "labels": {
+      "items": {
+        "properties": {
+          "color": {
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "default_color": {
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "id": {
+            "type": "number"
+          },
+          "name": {
+            "type": "string"
+          },
+          "order": {
+            "type": [
+              "number",
+              "null"
+            ]
+          }
+        },
+        "required": [
+          "id",
+          "name"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "total": {
+      "type": "number"
+    }
+  },
+  "required": [
+    "calendar_id",
+    "labels",
+    "total"
+  ],
+  "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.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered; the description adds useful behavior beyond that by disclosing the fixed set of 10 labels and the fields returned (ID, name, color, order). It does not discuss ordering semantics or whether labels can be missing, but the added context is real value, not repetition.

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?

Two tight sentences with zero waste. The core purpose is front-loaded and the downstream usage hint follows, so an agent can stop reading after the first clause if it only needs to know what the tool does.

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 single-parameter, read-only listing tool with an output schema and clear annotations, the description covers purpose, return contents, downstream use of the IDs, and the mutation alternative. Nothing an agent needs to invoke it correctly 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% and the single calendar_id parameter is fully documented in the schema, including the note that it comes from list_calendars. The description adds nothing about the parameter itself, so the baseline 3 applies; its added meaning ('use the IDs as label_id') concerns the return values, not the input.

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 ('List the 10 color labels of a calendar') and enumerates exactly what comes back: IDs, names, colors, and order. It is clearly distinguished from the sibling mutation tool update_calendar_labels, so an agent can pick it without opening the 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?

Explicitly directs the agent to feed the returned IDs in as label_id when creating or filtering events, and names update_calendar_labels as the tool for renaming or recoloring. It gives the alternative for the mutation path clearly, though it does not state a 'when not to call this' condition.

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