Skip to main content
Glama
boshyxd

Roblox Studio MCP Server

set_property

Modify property values of Roblox instances by specifying the instance path, property name, and desired value. Integrates with the Roblox Studio MCP Server to enable precise property adjustments.

Instructions

Set a property on any Roblox instance

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
instancePathYesPath to the instance (e.g., "game.Workspace.Part")
propertyNameYesName of the property to set
propertyValueYesValue to set the property to (any type)

Implementation Reference

  • The main handler function that executes the set_property tool by validating inputs and sending a request to the Studio HTTP client bridge to set the specified property on the instance.
    async setProperty(instancePath: string, propertyName: string, propertyValue: any) {
      if (!instancePath || !propertyName) {
        throw new Error('Instance path and property name are required for set_property');
      }
      const response = await this.client.request('/api/set-property', { 
        instancePath, 
        propertyName, 
        propertyValue 
      });
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(response, null, 2)
          }
        ]
      };
    }
  • JSON schema definition for the set_property tool inputs, including parameters, descriptions, and required fields.
      name: 'set_property',
      description: 'Set a property on any Roblox instance',
      inputSchema: {
        type: 'object',
        properties: {
          instancePath: {
            type: 'string',
            description: 'Path to the instance (e.g., "game.Workspace.Part")'
          },
          propertyName: {
            type: 'string',
            description: 'Name of the property to set'
          },
          propertyValue: {
            description: 'Value to set the property to (any type)'
          }
        },
        required: ['instancePath', 'propertyName', 'propertyValue']
      }
    },
  • src/index.ts:676-678 (registration)
    Registration and dispatching logic in the MCP CallToolRequest handler that routes set_property calls to the tools.setProperty method.
    case 'set_property':
      return await this.tools.setProperty((args as any)?.instancePath as string, (args as any)?.propertyName as string, (args as any)?.propertyValue);
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool performs a write operation ('Set'), implying mutation, but doesn't mention permissions, side effects, error handling, or whether changes are reversible. This is inadequate for a mutation tool with zero annotation coverage.

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 with zero waste. It's appropriately sized and front-loaded, directly stating the tool's purpose without unnecessary elaboration.

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 (a mutation operation with 3 parameters), lack of annotations, and no output schema, the description is insufficient. It doesn't explain return values, error conditions, or behavioral nuances, leaving significant gaps for an AI agent to understand how to use it correctly.

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?

The schema description coverage is 100%, so the input schema already documents all three parameters thoroughly. The description adds no additional meaning beyond what the schema provides, such as examples of property names or value types, resulting in a baseline score.

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 ('Set') and target ('a property on any Roblox instance'), providing a specific verb+resource combination. However, it doesn't differentiate from sibling tools like 'mass_set_property' or 'set_calculated_property', which prevents a perfect score.

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 is provided about when to use this tool versus alternatives like 'mass_set_property' for bulk operations or 'set_calculated_property' for computed values. The description lacks context about prerequisites, exclusions, or typical use cases.

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