Skip to main content
Glama
boshyxd

Roblox Studio MCP Server

get_instance_properties

Retrieve all properties of a specific instance in Roblox Studio by providing its instance path, enabling efficient access to instance data for development and debugging.

Instructions

Get all properties of a specific instance

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
instancePathYesPath to the instance

Implementation Reference

  • The core handler function that validates the instancePath input, makes an HTTP request to the Studio bridge for instance properties, and formats the JSON response for MCP.
    async getInstanceProperties(instancePath: string) {
      if (!instancePath) {
        throw new Error('Instance path is required for get_instance_properties');
      }
      const response = await this.client.request('/api/instance-properties', { instancePath });
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(response, null, 2)
          }
        ]
      };
    }
  • The input schema definition registered for listTools, specifying the required 'instancePath' parameter and tool description.
      name: 'get_instance_properties',
      description: 'Get all properties of a specific instance',
      inputSchema: {
        type: 'object',
        properties: {
          instancePath: {
            type: 'string',
            description: 'Path to the instance'
          }
        },
        required: ['instancePath']
      }
    },
  • src/index.ts:662-663 (registration)
    The MCP server request handler dispatches 'get_instance_properties' calls to the tools.getInstanceProperties method.
    case 'get_instance_properties':
      return await this.tools.getInstanceProperties((args as any)?.instancePath as string);
  • HTTP endpoint registration that proxies direct HTTP calls to the getInstanceProperties tool handler for Studio plugin compatibility.
    app.post('/mcp/get_instance_properties', async (req, res) => {
      try {
        const result = await tools.getInstanceProperties(req.body.instancePath);
        res.json(result);
      } catch (error) {
        res.status(500).json({ error: error instanceof Error ? error.message : 'Unknown error' });
      }
    });
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 states 'Get all properties' but doesn't clarify what 'properties' entail (e.g., metadata, attributes), whether this is a read-only operation, if there are permissions required, or how results are formatted. This leaves significant gaps for a tool with no 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 that directly states the tool's purpose without unnecessary words. It's appropriately sized and front-loaded, making it easy for an agent to parse quickly.

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 lack of annotations and output schema, the description is incomplete. It doesn't explain what 'properties' include, the return format, or behavioral aspects like error handling. For a tool that retrieves data, this leaves the agent with insufficient context to use it effectively.

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 description adds minimal meaning beyond the input schema, which has 100% coverage and documents the single parameter 'instancePath' as a string path. The description implies the parameter identifies an instance but doesn't elaborate on format or constraints, so it meets the baseline for high schema coverage without adding value.

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 ('Get') and resource ('properties of a specific instance'), making the purpose understandable. However, it doesn't distinguish this tool from similar siblings like 'get_instance_children' or 'mass_get_property', which could also retrieve instance-related data, so it doesn't reach the highest 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?

The description provides no guidance on when to use this tool versus alternatives. With many sibling tools like 'get_instance_children' and 'mass_get_property' that might retrieve related data, there's no indication of context, prerequisites, or exclusions, leaving the agent to guess based on tool names alone.

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