VRChat MCP

Overview Schema Source Related Servers Discussions Admin

vrchat_event_create

Create a group calendar event for a VRChat group with title, start and end times, description, and optional recurrence or tags.

Instructions

Create a group calendar event.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`tags`	No
`title`	Yes
`endsAt`	Yes
`groupId`	Yes
`imageId`	No
`isDraft`	No
`roleIds`	No
`category`	No		other
`featured`	No
`parentId`	No
`startsAt`	Yes
`languages`	No
`platforms`	No
`accessType`	No		group
`recurrence`	No
`description`	Yes
`occurrenceKind`	No	Recurring schedules require explicit series.
`hostEarlyJoinMinutes`	No
`usesInstanceOverflow`	No
`guestEarlyJoinMinutes`	No
`sendCreationNotification`	No
`closeInstanceAfterEndMinutes`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`event`	No
`result`	No
`status`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.1.15Sep 11, 2026

addedInput schema / properties / occurrenceKind

Added value: +{
+  "description": "Recurring schedules require explicit series.",
+  "enum": [
+    "single",
+    "series"
+  ],
+  "type": "string"
+}

addedInput schema / properties / recurrence

Added value: +{
+  "anyOf": [
+    {
+      "additionalProperties": {},
+      "properties": {
+        "daysOfWeek": {
+          "items": {
+            "enum": [
+              "FR",
+              "MO",
+              "SA",
+              "SU",
+              "TH",
+              "TU",
+              "WE"
+            ],
+            "type": "string"
+          },
+          "type": "array"
+        },
+        "end": {
+          "additionalProperties": {},
+          "properties": {
+            "count": {
+              "maximum": 9007199254740991,
+              "minimum": 1,
+              "type": "integer"
+            },
+            "date": {
+              "type": "string"
+            },
+            "type": {
+              "default": "afterDate",
+              "enum": [
+                "afterDate",
+                "afterOccurrences"
+              ],
+              "type": "string"
+            }
+          },
+          "type": "object"
+        },
+        "frequency": {
+          "default": "weekly",
+          "enum": [
+            "daily",
+            "monthly",
+            "weekly",
+            "yearly"
+          ],
+          "type": "string"
+        },
+        "interval": {
+          "maximum": 9007199254740991,
+          "minimum": 1,
+          "type": "integer"
+        },
+        "timezone": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "interval",
+        "timezone"
+      ],
+      "type": "object"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}

Changed2 schema fields changedv0.1.13Sep 6, 2026

changedInput schema / properties / endsAt / pattern

Previous value: -"^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d(?::[0-5]\\d(?:\\.\\d+)?)?(?:Z|([+-](?:[01]\\d|2[0-3]):[0-5]\\d)))$"New value: +"^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d:[0-5]\\d(?:\\.\\d+)?(?:Z|([+-](?:[01]\\d|2[0-3]):[0-5]\\d)))$"

changedInput schema / properties / startsAt / pattern

Previous value: -"^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d(?::[0-5]\\d(?:\\.\\d+)?)?(?:Z|([+-](?:[01]\\d|2[0-3]):[0-5]\\d)))$"New value: +"^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d:[0-5]\\d(?:\\.\\d+)?(?:Z|([+-](?:[01]\\d|2[0-3]):[0-5]\\d)))$"

First observedv0.1.8Jul 29, 2026

TDQS

C2.4/5.0

Behavior2/5

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

readOnlyHint=false confirms this is a mutation, and the description's 'Create' is consistent with that. However, with a 22-parameter write operation the description discloses nothing about required permissions, whether creation triggers notifications, defaults for accessType/isDraft, or what side effects occur — a substantial gap given minimal annotation coverage.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single grammatically complete sentence with zero waste and the verb front-loaded. It is concise to a fault: for a tool this complex, the content is under-specified rather than efficiently trimmed.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need no explanation, but the description still omits everything an agent needs to invoke a 22-parameter group event creation correctly. It is far too thin for the schema's complexity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 5% (only occurrenceKind is documented), leaving 21 parameters including required fields with no embedded explanation. The description adds nothing about any parameter, so it fails to compensate for the coverage gap on a large schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (create) and resource (group calendar event), so an agent immediately knows the operation. It does not differentiate itself from close siblings like vrchat_event_update or vrchat_group_event_get, but the create/read distinction is inferable from the verb.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

There is no guidance on when to use this tool versus vrchat_event_update, vrchat_instance_create, or vrchat_group_post_create, nor any prerequisites such as group membership or permissions. Usage is only implied by the verb.

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

Deploy Server