list_rules
List all UdonSharp rules from the repository, with optional filtering by skill.
Instructions
List all UdonSharp rules from the repository
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| skillId | No | Filter rules by skill |
VRChat Udon MCP
by elmau21
Schema Changelog
Changes observed during successful MCP inspections.
- First observed
v2.0.0
TDQS
B3.1/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations, description only states listing behavior; lacks details on pagination, side effects, or data handling.
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?
Single concise sentence with no redundancy.
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?
Given simplicity, covers basic purpose but misses return format hint and usage context relative to siblings.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters3/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema covers 100%, description adds minimal context about optional filtering but no details on filter matching.
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?
States explicit action 'list all rules' and specific repository context, but does not differentiate from sibling list tools like list_skills or list_templates.
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?
No guidance on when to use listing vs searching or reading individual rules; alternative tools present.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.