Skip to main content
Glama
boshyxd

Roblox Studio MCP Server

search_by_property

Locate objects in Roblox Studio by specifying a property name and value, enabling precise identification of elements within your project.

Instructions

Find objects with specific property values

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
propertyNameYesName of the property to search
propertyValueYesValue to search for

Implementation Reference

  • The main execution handler for the 'search_by_property' MCP tool. Validates parameters, sends request to Studio bridge API endpoint '/api/search-by-property', and formats response as MCP content.
    async searchByProperty(propertyName: string, propertyValue: string) {
      if (!propertyName || !propertyValue) {
        throw new Error('Property name and value are required for search_by_property');
      }
      const response = await this.client.request('/api/search-by-property', { 
        propertyName, 
        propertyValue 
      });
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(response, null, 2)
          }
        ]
      };
    }
  • MCP tool schema registration in ListToolsRequestSchema response, defining name, description, and input schema for 'search_by_property'.
    {
      name: 'search_by_property',
      description: 'Find objects with specific property values',
      inputSchema: {
        type: 'object',
        properties: {
          propertyName: {
            type: 'string',
            description: 'Name of the property to search'
          },
          propertyValue: {
            type: 'string',
            description: 'Value to search for'
          }
        },
        required: ['propertyName', 'propertyValue']
      }
    },
  • src/index.ts:666-667 (registration)
    Tool dispatch registration in the MCP CallToolRequestSchema handler switch statement, routing calls to the tools.searchByProperty method.
    case 'search_by_property':
      return await this.tools.searchByProperty((args as any)?.propertyName as string, (args as any)?.propertyValue as string);
  • HTTP proxy endpoint registration for 'search_by_property' tool, allowing direct HTTP calls from Studio plugin via /mcp/search_by_property.
    app.post('/mcp/search_by_property', async (req, res) => {
      try {
        const result = await tools.searchByProperty(req.body.propertyName, req.body.propertyValue);
        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 full burden. It mentions 'Find objects' but doesn't disclose behavioral traits such as read-only vs. destructive operations, authentication needs, rate limits, or return format. This is a significant gap for a search tool with no structured safety hints.

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 no wasted words. It's front-loaded and appropriately sized for its purpose, making it easy 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 no annotations, no output schema, and a search function with siblings, the description is incomplete. It doesn't explain what 'objects' refer to, how results are returned, or constraints, leaving the agent with insufficient context for effective use.

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 schema already documents both parameters ('propertyName' and 'propertyValue'). The description adds no additional meaning beyond implying property-based searching, which is already clear from the schema. Baseline 3 is appropriate as the schema does the heavy lifting.

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

Purpose3/5

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

The description 'Find objects with specific property values' clearly states the tool's purpose with a verb ('Find') and resource ('objects'), but it's vague about what type of objects and lacks differentiation from sibling tools like 'search_objects' or 'search_files'. It provides a basic function but doesn't specify scope or uniqueness.

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 'search_objects' and 'search_files', the description doesn't indicate if this is for general object searches, property-based filtering, or specific contexts, leaving usage ambiguous.

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