Skip to main content
Glama
BASIC-BIT

VRChat MCP

by BASIC-BIT
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

vrchat_favorites

Read-only

Read VRChat favorites and favorite groups, check limits, or list favorited avatars. Use filters like type, tag, or user for compact, read-only results.

Instructions

Read favorites, favorite groups, limits, or favorited avatars with compact outputs (read-only).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tagNo
sortNo
typeNoFavorite type. For groups, filters the collection list.
viewNofavorites
notagNo
orderNo
queryNo
offsetNo
userIdNo
ownerIdNo
featuredNo
maxItemsNo
maxPagesNo
pageSizeNo
platformNo
releaseStatusNo
maxUnityVersionNo
minUnityVersionNo
favoriteGroupNameNo
favoriteGroupTypeNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNo
viewYes
groupNo
notesNo
totalNo
groupsNo
limitsNo
avatarsNo
favoritesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.1.15
    • changedInput schema / properties / favoriteGroupType / enum
      Previous value: -[
-  "avatar",
-  "friend",
-  "world"
-]New value: +[
+  "avatar",
+  "friend",
+  "vrcPlusWorld",
+  "world"
+]
    • addedInput schema / properties / type / description
      Added value: +"Favorite type. For groups, filters the collection list."
    • changedInput schema / properties / type / enum
      Previous value: -[
-  "avatar",
-  "friend",
-  "world"
-]New value: +[
+  "avatar",
+  "friend",
+  "vrcPlusWorld",
+  "world"
+]
  2. First observedv0.1.8

TDQS

B3/5.0
Behavior3/5

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

The annotation already declares readOnlyHint=true, so '(read-only)' adds little. 'Compact outputs' is a useful behavioral hint about return shape, but the description does not mention pagination, auth requirements, rate limits, or how filtering affects results.

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?

It is a single, front-loaded sentence with no filler. Every clause carries purpose or scope, making it appropriately concise for a tool summary.

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

Completeness2/5

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

For a read tool with 20 parameters, 5% schema description coverage, and no required fields, the description is too thin. An output schema exists, so return values need not be explained, but the agent gets very little help understanding how to use the many filtering and pagination parameters.

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 only 5% for 20 parameters. The description loosely maps to view categories ('favorites, favorite groups, limits, or favorited avatars'), but it leaves most parameters — tag, sort, order, offset, userId, ownerId, platform, releaseStatus, etc. — completely unexplained.

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 uses a specific verb ('Read') and names the resources ('favorites, favorite groups, limits, or favorited avatars'), so the agent understands the tool's domain. It stops short of distinguishing itself from siblings like vrchat_favorite_add, vrchat_favorite_remove, or vrchat_worlds_favorites.

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

Usage Guidelines2/5

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

The description offers no explicit when-to-use guidance, no prerequisites, and no named alternatives. The parenthetical '(read-only)' implies it should be used for viewing rather than mutation, but the agent receives no routing instruction.

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