Skip to main content
Glama
boshyxd

Roblox Studio MCP Server

get_class_info

Retrieve properties and methods for specified Roblox classes to streamline development in Roblox Studio. Simplify access to class details for enhanced scripting and project management.

Instructions

Get available properties/methods for Roblox classes

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
classNameYesRoblox class name

Implementation Reference

  • Core handler function that validates input, requests class information from the Studio HTTP client, and formats the response as MCP content.
    async getClassInfo(className: string) {
      if (!className) {
        throw new Error('Class name is required for get_class_info');
      }
      const response = await this.client.request('/api/class-info', { className });
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(response, null, 2)
          }
        ]
      };
    }
  • Tool schema definition including name, description, and input schema requiring 'className' string.
    name: 'get_class_info',
    description: 'Get available properties/methods for Roblox classes',
    inputSchema: {
      type: 'object',
      properties: {
        className: {
          type: 'string',
          description: 'Roblox class name'
        }
      },
      required: ['className']
    }
  • src/index.ts:668-669 (registration)
    MCP tool dispatcher registration in the CallToolRequestHandler switch case, calling the handler.
    case 'get_class_info':
      return await this.tools.getClassInfo((args as any)?.className as string);
  • HTTP proxy endpoint registration for get_class_info tool calls.
    app.post('/mcp/get_class_info', async (req, res) => {
      try {
        const result = await tools.getClassInfo(req.body.className);
        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 the tool retrieves information ('Get'), implying a read-only operation, but doesn't specify details like response format, error handling, rate limits, or authentication needs. For a tool with zero annotation coverage, this is a significant gap in transparency.

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 front-loaded and wastes no space, 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 the tool returns (e.g., a list of properties/methods, their types, or inheritance details), error cases, or usage context. For a tool with no structured output information, the description should provide more behavioral and output details to be fully helpful.

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%, with the single parameter 'className' clearly documented as 'Roblox class name'. The description adds no additional parameter semantics beyond what the schema provides, such as examples or constraints. With high schema coverage, the baseline is 3, as the description doesn't compensate but also doesn't detract.

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 tool's purpose with a specific verb ('Get') and resource ('available properties/methods for Roblox classes'). It distinguishes itself from siblings like get_instance_properties or get_place_info by focusing on class metadata rather than instance or place data. However, it doesn't explicitly contrast with all siblings, so it's not a perfect 5.

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. It doesn't mention prerequisites (e.g., needing a valid class name), exclusions, or compare it to similar tools like get_instance_properties or get_services. This leaves the agent with minimal context for tool 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