VRChat MCP

Overview Schema Source Related Servers Discussions Admin

vrchat_status_page_overview

Read-only

Get VRChat's status overview: up/down state, graph min/max/current, recent incidents, and active or upcoming maintenance. Read-only summary helps determine if issues affect you.

Instructions

Compact VRChat status-page overview: up/down state, graph min/max/current values, unresolved + recent incidents, and active + upcoming maintenance (read-only).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`maxItems`	No
`recentHours`	No
`includeGraphs`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`page`	Yes
`notes`	Yes
`graphs`	Yes
`status`	Yes
`maxItems`	Yes
`checkedAt`	Yes
`incidents`	Yes
`components`	Yes
`recentHours`	Yes
`maintenances`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed12 schema fields changedv0.1.13Sep 6, 2026
- removedOutput schema / properties / graphs / items / properties / current / anyOf
```
Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / graphs / items / properties / current / type
```
Added value: +[
+  "number",
+  "null"
+]
```
- removedOutput schema / properties / graphs / items / properties / max / anyOf
```
Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / graphs / items / properties / max / type
```
Added value: +[
+  "number",
+  "null"
+]
```
- removedOutput schema / properties / graphs / items / properties / min / anyOf
```
Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / graphs / items / properties / min / type
```
Added value: +[
+  "number",
+  "null"
+]
```
- removedOutput schema / properties / graphs / items / properties / overlayCurrent / anyOf
```
Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / graphs / items / properties / overlayCurrent / type
```
Added value: +[
+  "number",
+  "null"
+]
```
- removedOutput schema / properties / graphs / items / properties / overlayMax / anyOf
```
Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / graphs / items / properties / overlayMax / type
```
Added value: +[
+  "number",
+  "null"
+]
```
- removedOutput schema / properties / graphs / items / properties / overlayMin / anyOf
```
Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / graphs / items / properties / overlayMin / type
```
Added value: +[
+  "number",
+  "null"
+]
```
First observedv0.1.8Jul 29, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already include readOnlyHint=true, and the description reinforces this with '(read-only)'. It also adds behavioral context by disclosing the coverage of the overview: up/down state, graph values, incidents, and maintenance windows, which helps the agent understand what data to expect and that this is a compact summary rather than a detailed operational report.

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 that efficiently uses a colon-delimited list to enumerate the returned content. There is no filler or redundant restating of the tool name.

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 presence of an output schema covers the return structure, and the description lists the main content areas and read-only nature. However, the lack of parameter semantics and any usage guidance leaves some gaps for an agent deciding how to invoke the tool with the optional arguments.

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 the three parameters at all. While the parameter names (maxItems, recentHours, includeGraphs) and schema constraints give some hints, there is ambiguity about what maxItems applies to, what recentHours covers, and what happens when includeGraphs is omitted.

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 the resource (VRChat status page) and the specific content delivered: up/down state, graph min/max/current values, unresolved and recent incidents, and active/upcoming maintenance. This is distinct enough from sibling tools such as vrchat_operations or vrcx_db_status to avoid confusion.

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 read-only status-page purpose makes the use case fairly obvious, but the description does not explicitly say when to choose this tool over alternatives or mention any exclusions. There is no direct sibling comparison or routing guidance, so the usage context is implied rather than stated.

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

Deploy Server