Skip to main content
Glama
Sign In
Roblox Studio MCP Server

Roblox Studio MCP Server

by boshyxd
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

create_object_with_properties

Generate and configure Roblox objects with specific properties in Roblox Studio, defining class, parent, name, and attributes directly upon creation.

Instructions

Create a new Roblox object instance with initial properties

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "className": "<className>",
      "parent": "<parent>"
    },
    "name": "create_object_with_properties"
  }
}

Input Schema

NameRequiredDescriptionDefault
classNameYesRoblox class name (e.g., "Part", "Script", "Folder")
nameNoOptional name for the new object
parentYesPath to the parent instance (e.g., "game.Workspace")
propertiesNoProperties to set on creation

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
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. It states that creation occurs, but gives no details about side effects, error conditions, permissions, return value, or behavior when the parent path is invalid. This is minimal transparency for a mutation tool.

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, front-loaded sentence with no wasted words. Every word earns its place, making it highly concise.

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 tool with 4 parameters, no output schema, and no annotations, the description is too sparse. It does not explain the creation workflow, return value, or relationship to sibling tools, leaving the agent underinformed for effective invocation.

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 baseline is 3. The description's mention of 'initial properties' does not add information beyond the schema's property descriptions. There is no additional semantic detail for parameters.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description specifies a clear action ('Create a new Roblox object instance') and adds the differentiator 'with initial properties', distinguishing it from sibling tools like create_object. This is a specific verb+resource with scope.

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 on when to use this tool versus alternatives such as create_object or mass_create_objects_with_properties. The description implies usage through the name but does not state exclusions or alternatives.

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

Related Tools