TimeTree MCP Server

get_calendar_virtual_members

Read-only

List a calendar’s virtual members—people or things without TimeTree accounts, such as a child, pet, or car—so you can assign events to them and retrieve IDs for updates.

Instructions

List the virtual members of a calendar: people or things without a TimeTree account, such as a child, pet, or car, that events can be assigned to. Returns id (for virtual_user_attendees on events) and uuid (to update or delete the member). For members with accounts use get_calendar_members.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`calendar_id`	Yes	The calendar ID from list_calendars (numeric string; numbers are also accepted)
`include_deactivated`	No	Include deactivated virtual members (default: false)

Output Schema

TableJSON Schema

Name	Required	Description	Default
`total`	Yes
`calendar_id`	Yes
`virtual_members`	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"
+    },
+    "total": {
+      "type": "number"
+    },
+    "virtual_members": {
+      "items": {
+        "properties": {
+          "birthday": {
+            "type": [
+              "string",
+              "number",
+              "null"
+            ]
+          },
+          "calendar_id": {
+            "type": [
+              "number",
+              "string"
+            ]
+          },
+          "created_at": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "id": {
+            "description": "Use in virtual_user_attendees of events",
+            "type": [
+              "string",
+              "number"
+            ]
+          },
+          "is_active": {
+            "type": "boolean"
+          },
+          "name": {
+            "type": "string"
+          },
+          "one_word": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "shows_birthday": {
+            "type": [
+              "boolean",
+              "null"
+            ]
+          },
+          "type": {
+            "description": "child, pet, car, grandfather, grandmother, or other",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "updated_at": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "uuid": {
+            "description": "Use as virtual_member_uuid to update or delete",
+            "type": [
+              "string",
+              "null"
+            ]
+          }
+        },
+        "required": [
+          "id",
+          "name",
+          "is_active"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "calendar_id",
+    "virtual_members",
+    "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.5/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 the safety profile is covered; the description adds that the call is scoped to a single calendar and clarifies the meaning of the two returned identifiers and what each is good for. It does not discuss pagination, how deactivated members appear, or the open-world implication of account-less entities, leaving modest gaps against the annotation baseline.

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 tight sentences, front-loaded with purpose and the definition, then return-value roles, then the alternative tool. Nothing is repeated from the schema or annotations and no sentence is filler.

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?

With an output schema present, the description needn't restate return structure and instead explains what the returned ids are for, plus a clear sibling routing rule and a definition of the resource. For a two-parameter read tool this leaves nothing an agent needs 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% with per-parameter descriptions (calendar_id sourced from list_calendars, include_deactivated with its default), so the structured data already carries the meaning. The description adds no parameter-level detail beyond implying calendar scoping; baseline 3 applies when the schema does the heavy lifting.

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+resource ('List the virtual members of a calendar') plus a plain-language definition of what a virtual member is (a person or thing without a TimeTree account, e.g. child, pet, car). It explicitly contrasts with the account-holder equivalent and names the sibling that handles those, so the 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 Guidelines5/5

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

Names the alternative explicitly ('For members with accounts use get_calendar_members') and the condition that selects it, which is the exact routing decision an agent faces between this tool and its sibling. It also signals downstream use ('id for virtual_user_attendees on events', 'uuid to update or delete the member'), which tells the agent why it would call this first.

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