VRChat MCP

Overview Schema Source Related Servers Discussions Admin

vrcx_db_status

Read-only

Detect if VRCX is installed, then report its database path, active user, and version. A read-only status check for VRChat local data.

Instructions

Detect VRCX on this machine and report database path, active user, and DB version (read-only).

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description	Default
`db`	Yes
`enabled`	Yes
`worldDb`	Yes
`vrcxJson`	Yes
`warnings`	No
`available`	Yes
`userPrefix`	Yes
`activeUserId`	Yes
`databaseVersion`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed10 schema fields changedv0.1.13Sep 6, 2026
- removedOutput schema / properties / activeUserId / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / activeUserId / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / db / properties / path / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / db / properties / path / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / userPrefix / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / userPrefix / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / vrcxJson / properties / path / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / vrcxJson / properties / path / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / worldDb / properties / path / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / worldDb / properties / path / type
```
Added value: +[
+  "string",
+  "null"
+]
```
First observedv0.1.8Jul 29, 2026

TDQS

A4.5/5.0

Behavior4/5

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

The description explicitly states 'read-only', reinforcing the readOnlyHint annotation, and adds behavioral context beyond it: the tool detects VRCX locally and reports specific database fields. It does not cover failure behavior when VRCX is absent, but for a zero-parameter read-only check this is a minor gap.

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?

A single, compact sentence states the action, scope, and specific outputs with no filler. The essential 'read-only' qualifier is included and the sentence is front-loaded with the primary purpose.

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?

For a zero-parameter read-only diagnostic tool with an output schema present, the description is sufficiently complete. An agent knows what the tool does, what it reports, and that it is safe to invoke. No additional invocation details are needed.

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

Parameters4/5

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

There are no parameters, so the description carries no parameter burden. Schema coverage is effectively 100% because the schema is empty and complete for this tool. The description appropriately focuses on the tool's purpose rather than parameters.

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 clearly states a specific action (detect/report) and a concrete resource (VRCX database status), and names the exact outputs: database path, active user, and DB version. It is not a tautology and is easily distinguished from sibling tools like vrcx_memos or vrchat_* tools.

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

Usage Guidelines4/5

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

The description implies appropriate use: when you need to check whether VRCX is present and obtain its local database information. It does not explicitly name alternatives or exclusions, but the zero-parameter read-only nature and unique scope make the usage context reasonably clear.

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

Deploy Server