VRChat MCP

Overview Schema Source Related Servers Discussions Admin

vrchat_me

Read-only

Fetch your VRChat profile using summary, presence, or profile presets, override fields, and optionally include a paginated list of your groups.

Instructions

Get your profile (read-only). Use view=presence/summary/profile presets; provide fields to override. Optionally include a paged list of your groups.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`view`	No
`fields`	No
`compact`	No
`groupOffset`	No
`groupMaxPages`	No
`groupPageSize`	No
`includeGroups`	No
`maxArrayLength`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`user`	Yes
`groups`	No
`userId`	Yes
`vrcxMemo`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedv0.1.13Sep 6, 2026
- removedOutput schema / properties / vrcxMemo / properties / editedAt / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / vrcxMemo / properties / editedAt / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / vrcxMemo / properties / memo / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / vrcxMemo / properties / memo / type
```
Added value: +[
+  "string",
+  "null"
+]
```
First observedv0.1.8Jul 29, 2026

TDQS

A3.7/5.0

Behavior4/5

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

The description reinforces the readOnlyHint annotation by stating 'read-only' and adds behavioral context: view presets control the response shape, fields override presets, and groups can be included as a paged list. This goes beyond what the annotations alone provide without contradicting them.

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?

The description is two succinct sentences with no wasted words. It front-loads the core purpose and read-only nature, then provides the key usage details in a compact, easy-to-scan structure.

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

Completeness3/5

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

The description covers the main behaviors: read-only retrieval, view presets, field overrides, and optional group paging. An output schema exists and likely documents return values, but the tool has eight optional parameters and two of them, compact and maxArrayLength, receive no explanation. This leaves the description adequate but incomplete for full parameter understanding.

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 0%, so the description must compensate for the eight unnamed parameters. It explains view, fields, and the group-related pagination parameters reasonably well by referencing presets, overrides, and 'a paged list of your groups.' However, compact and maxArrayLength are not explained, leaving notable gaps.

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?

The description states a specific verb and resource: 'Get your profile (read-only).' This clearly identifies the tool as retrieving the caller's own profile rather than another user's or avatar's profile. It does not explicitly name sibling tools such as vrchat_user_profile or vrchat_avatar_profile, so it stops slightly short of full differentiation.

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

Usage Guidelines3/5

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

The description gives concrete usage instructions: use view presets, override with fields, and optionally include paged groups. It implies this tool is for the caller's own profile but does not explicitly state when to choose it over alternatives or list exclusions among the many sibling profile/read tools.

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

Deploy Server