Skip to main content
Glama
boshyxd

Roblox Studio MCP Server

set_relative_property

Adjust properties of instances in Roblox Studio by performing mathematical operations like add, subtract, multiply, divide, or power on their current values, specified by paths and property names.

Instructions

Modify properties relative to their current values

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
componentNoSpecific component for Vector3/UDim2 properties
operationYesMathematical operation to perform
pathsYesArray of instance paths to modify
propertyNameYesName of the property to modify
valueYesValue to use in the operation

Implementation Reference

  • The handler function that executes the set_relative_property tool. Validates parameters and sends HTTP request to the Studio bridge API endpoint '/api/set-relative-property'.
    async setRelativeProperty(
      paths: string[], 
      propertyName: string, 
      operation: 'add' | 'multiply' | 'divide' | 'subtract' | 'power',
      value: any,
      component?: 'X' | 'Y' | 'Z' // For Vector3/UDim2 properties
    ) {
      if (!paths || paths.length === 0 || !propertyName || !operation || value === undefined) {
        throw new Error('Paths, property name, operation, and value are required for set_relative_property');
      }
      const response = await this.client.request('/api/set-relative-property', { 
        paths, 
        propertyName, 
        operation,
        value,
        component
      });
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(response, null, 2)
          }
        ]
      };
    }
  • Defines the tool schema including description, input parameters, types, and validation rules for set_relative_property.
      name: 'set_relative_property',
      description: 'Modify properties relative to their current values',
      inputSchema: {
        type: 'object',
        properties: {
          paths: {
            type: 'array',
            items: { type: 'string' },
            description: 'Array of instance paths to modify'
          },
          propertyName: {
            type: 'string',
            description: 'Name of the property to modify'
          },
          operation: {
            type: 'string',
            enum: ['add', 'multiply', 'divide', 'subtract', 'power'],
            description: 'Mathematical operation to perform'
          },
          value: {
            description: 'Value to use in the operation'
          },
          component: {
            type: 'string',
            enum: ['X', 'Y', 'Z'],
            description: 'Specific component for Vector3/UDim2 properties'
          }
        },
        required: ['paths', 'propertyName', 'operation', 'value']
      }
    },
  • src/index.ts:708-709 (registration)
    Registers the tool handler dispatch in the MCP CallToolRequestSchema switch statement, mapping the tool name to the RobloxStudioTools.setRelativeProperty method.
    case 'set_relative_property':
      return await this.tools.setRelativeProperty((args as any)?.paths as string[], (args as any)?.propertyName as string, (args as any)?.operation, (args as any)?.value, (args as any)?.component);
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions 'modify' (implying mutation) but lacks details on permissions, side effects, error handling, or output format. For a mutation tool with zero annotation coverage, this is a significant gap, though it doesn't contradict any 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 a single, efficient sentence that front-loads the core purpose without unnecessary words. Every part earns its place by succinctly conveying the tool's relative modification nature, making it easy to parse.

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?

Given the tool's complexity (mutation with 5 parameters, no output schema, and no annotations), the description is incomplete. It doesn't explain the return values, error conditions, or practical use cases, leaving gaps that could hinder an agent's ability to invoke it correctly in context.

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 description coverage is 100%, so the schema already documents all five parameters (e.g., 'operation' with enum values like 'add', 'paths' as array of instance paths). The description adds no additional meaning beyond the schema, such as examples or constraints, but the baseline is 3 when schema coverage is high.

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 'Modify properties relative to their current values' clearly states the tool's function with a specific verb ('modify') and resource ('properties'), and the 'relative' aspect distinguishes it from absolute property-setting tools like 'set_property' or 'mass_set_property' among the siblings. However, it doesn't explicitly name the sibling alternatives or detail the exact scope of modification.

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 provides no explicit guidance on when to use this tool versus alternatives. While the 'relative' aspect implies it's for incremental changes rather than absolute setting, it doesn't specify scenarios, prerequisites, or exclusions compared to tools like 'set_property' or 'set_calculated_property'. This leaves the agent with minimal context for selection.

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

Install Server

Other Tools

Related Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/boshyxd/robloxstudio-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server