VRChat MCP

Overview Schema Source Related Servers Discussions Admin

vrcx_instances_recent

Read-only

Review recently visited VRChat instances from your VRCX account history. Filter results by number of sessions or days back to see where you've been.

Instructions

List recent instance sessions for your active VRCX account (read-only). Derived from VRCX gamelog OnPlayerLeft entries.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No
`daysBack`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`from`	Yes
`limit`	Yes
`total`	Yes
`sessions`	Yes
`truncated`	Yes
`activeUserId`	No

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

A3.9/5.0

Behavior4/5

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

The readOnlyHint annotation already covers safety, and the description adds meaningful context beyond it by revealing the data source (VRCX gamelog OnPlayerLeft entries) and the account scope. This helps the agent understand the data is locally derived from gamelog events rather than a live VRChat API query.

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 a single front-loaded sentence with no filler. It conveys the action, scope, read-only nature, and data provenance efficiently, covering the essential points without redundancy.

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

Completeness4/5

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

For a low-complexity read-only tool with an output schema, two optional parameters, and a clear annotation, the description is largely sufficient. It provides the key context about the source and scope, though it could be slightly stronger with an explicit usage comparison to sibling tools.

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

Parameters2/5

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

Schema description coverage is 0%, and the description does not explain limit or daysBack beyond the word 'recent,' which only loosely maps to daysBack. The parameter names are somewhat self-explanatory, but the description does not compensate for the missing schema-level documentation, defaults, or exact meaning of the limit parameter.

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?

The description states a specific verb ('List'), a specific resource ('recent instance sessions'), and a clear scope ('your active VRCX account'). It also adds the source ('gamelog OnPlayerLeft entries'), which helps distinguish this tool from the broader VRChat API and sibling VRCX log-based tools.

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 implies usage for retrieving recent instance sessions from a VRCX account and indicates a read-only operation, but it does not explicitly state when to prefer this tool over related siblings like vrcx_gamelog_world_visits_recent or vrcx_user_relationship_sessions. The guidance is implicit rather than explicit.

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

Deploy Server