Skip to main content
Glama
Roblox Studio MCP Gateway

Roblox Studio MCP Gateway

by camilin7483

roblox_toolbox

Search Creator Store assets, insert assets by ID into a chosen parent, or preview a single asset before insertion.

Instructions

Toolbox gateway: insert ids, preview one asset, or search by query.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "roblox_toolbox"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryNo
parentNoWorkspace
insert_idsNo
preview_idNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.7/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are supplied, so the description carries the full behavioral burden. It does not disclose that inserting assets mutates the place, what 'parent' controls, whether inserts are reversible, or what permissions are required — all critical for a tool that can write into a workspace.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no filler, and the three modes are easy to scan. It is arguably too terse for a five-parameter gateway, but nothing in it is wasted.

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?

An output schema exists, so return values need not be explained, but for a five-parameter, zero-annotation, multi-mode mutation tool the description leaves mode selection, the parent/limit parameters, and side effects entirely undocumented. It is not complete enough for reliable invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across five parameters, so the description must compensate and largely does not. It hints at insert_ids, preview_id, and query, but says nothing about 'parent' (default Workspace) or 'limit', nor about mutual exclusivity or defaults for the mode-selecting parameters.

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 names the resource (Toolbox) and enumerates three concrete operations: inserting ids, previewing a single asset, and searching by query. That is clear enough for an agent to know what the tool does, but it never distinguishes this from siblings like roblox_search or roblox_import, which plausibly overlap.

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?

It lists three modes but gives no guidance on when to choose this tool over roblox_search or roblox_import, and no indication of how a caller selects a mode (which parameter combination triggers insert vs preview vs search). The agent must reverse-engineer mode selection from the schema alone.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.