Skip to main content
Glama
BASIC-BIT

VRChat MCP

by BASIC-BIT
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

vrcx_user_relationship_sessions

Read-only

List recent shared instance sessions with a user from VRCX logs to review past meetings and interactions.

Instructions

List recent shared instance sessions with a user from VRCX logs (read-only). Use this for deep history; results are limited by default.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
userIdNo
displayNameNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitYes
queryYes
totalYes
sessionsYes
truncatedYes
resolvedByYes
resolvedUserIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv0.1.13
    • removedOutput schema / properties / resolvedUserId / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
    • addedOutput schema / properties / resolvedUserId / type
      Added value: +[
+  "string",
+  "null"
+]
    • 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"
+]
  2. First observedv0.1.8

TDQS

A3.7/5.0
Behavior4/5

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

The annotation already declares readOnlyHint=true, and the description reinforces the read-only nature while adding useful behavioral context: sessions come from VRCX logs and results are limited by default. No contradictions with the annotations.

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 one tight sentence that front-loads the action and resource, then adds the key usage and limitation context. Every clause contributes value with no wasted words.

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, annotations, and output schema cover the basic read-only listing behavior, but the undocumented parameters and lack of explicit sibling differentiation leave gaps. An agent can probably call it, but not with full confidence about parameter selection or default limits.

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 compensate by explaining what userId, displayName, or limit mean or how they relate. The phrase 'with a user' hints at the user parameters, but the agent is left to infer which identifier to use and how limit behaves.

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 clearly states the action ('List'), the resource ('recent shared instance sessions with a user'), and the data source ('from VRCX logs'). It does not explicitly name a sibling tool or explain how it differs from vrcx_user_relationship_summary, but 'deep history' signals a specific scope.

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 phrase 'Use this for deep history' gives a clear context for when this tool is appropriate. However, it does not name alternatives or state when not to use it, so it stops short of full routing guidance.

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

Deploy Server

Other Tools