Skip to main content
Glama
boshyxd

Roblox Studio MCP Server

get_services

Retrieve available Roblox services and their children for better integration and interaction with Roblox Studio projects using the MCP server.

Instructions

Get available Roblox services and their children

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
serviceNameNoOptional specific service name to query

Implementation Reference

  • Core handler function that executes the get_services tool by requesting '/api/services' from StudioHttpClient and returning formatted JSON response.
    async getServices(serviceName?: string) {
      const response = await this.client.request('/api/services', { serviceName });
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(response, null, 2)
          }
        ]
      };
    }
  • Input schema definition for the get_services tool, specifying optional serviceName parameter.
    name: 'get_services',
    description: 'Get available Roblox services and their children',
    inputSchema: {
      type: 'object',
      properties: {
        serviceName: {
          type: 'string',
          description: 'Optional specific service name to query'
        }
      }
    }
  • src/index.ts:656-657 (registration)
    MCP server request handler registration: dispatches get_services calls to the tools.getServices method.
    case 'get_services':
      return await this.tools.getServices((args as any)?.serviceName);
  • HTTP endpoint registration for /mcp/get_services, proxying requests to tools.getServices for Studio plugin compatibility.
    app.post('/mcp/get_services', async (req, res) => {
      try {
        const result = await tools.getServices(req.body.serviceName);
        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 data ('Get'), implying a read-only operation, but doesn't specify aspects like authentication requirements, rate limits, or what 'children' entails (e.g., depth, format). This leaves gaps in understanding the tool's behavior beyond basic purpose.

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 is front-loaded and appropriately sized, 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.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's low complexity (one optional parameter, no output schema) and the description's clear purpose, it is minimally complete. However, without annotations or output schema, it lacks details on behavioral traits and return values, which could hinder optimal agent usage in more complex scenarios.

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 input schema has 100% description coverage, with the parameter 'serviceName' documented as 'Optional specific service name to query'. The description adds no additional meaning beyond this, such as examples or constraints, so it meets the baseline for adequate but not enhanced parameter semantics.

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 target resources ('available Roblox services and their children'), making the tool's purpose understandable. It doesn't explicitly differentiate from sibling tools like 'get_class_info' or 'get_instance_children', which might also retrieve hierarchical information, so it misses 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?

No guidance is provided on when to use this tool versus alternatives. With siblings like 'get_class_info', 'get_instance_children', and 'get_project_structure' that might overlap in retrieving hierarchical data, the description lacks context on specific use cases or exclusions, leaving the agent to infer usage.

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