VRChat MCP

Overview Schema Source Related Servers Discussions Admin

vrcx_gamelog_world_visits_recent

Read-only

Find which VRChat worlds you visited recently by reading your local VRCX gamelog. Specify a time range or limit to review your activity history.

Instructions

List recent world visits from the VRCX gamelog (read-only). This reflects your local VRChat/VRCX activity history.

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
`visits`	Yes
`truncated`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.1.13Sep 6, 2026
- removedOutput schema / properties / visits / items / properties / groupName / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / visits / items / properties / groupName / 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 the safety profile, and the description reinforces it with '(read-only)' while adding useful context: the data is from a local gamelog and reflects local activity history. This helps the agent understand that the data may differ from live VRChat server state.

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 short sentences with no filler. The core operation and source are front-loaded, and the second sentence adds only relevant context about local activity history.

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 simple read-only list tool with an output schema and a readOnlyHint annotation, the description is largely complete. It explains the data source and local nature of the data, though it could marginally benefit from noting how limit and daysBack interact or what 'recent' means.

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%, so the description should compensate by explaining parameter behavior. It does not mention 'limit' or 'daysBack' at all. However, the parameter names are fairly self-explanatory and the schema provides min/max constraints, so this is a minor but noticeable gap.

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 ('world visits'), and a specific source ('VRCX gamelog'). It clearly distinguishes this from sibling tools by emphasizing local VRChat/VRCX activity history, making its scope unambiguous.

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 the tool is appropriate when looking at local activity history, but it does not explicitly state when to use this tool over alternatives or mention any exclusions. No sibling alternative is named or contrasted, so the agent must infer the intended use case.

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

Deploy Server