Skip to main content
Glama
Roblox Studio MCP Gateway

Roblox Studio MCP Gateway

by camilin7483

roblox_class

Retrieves the properties and events of a specified Roblox class to help you inspect its API and understand available members before scripting or editing instances.

Instructions

Class info: properties and events.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "class_name": "<class_name>"
    },
    "name": "roblox_class"
  }
}

Input Schema

NameRequiredDescriptionDefault
class_nameYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.4/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 disclosure burden, yet it says nothing about whether the call is read-only, whether it requires environment connectivity, or whether it accepts only built-in Roblox classes versus user-defined ones. An output schema exists, so return shape is covered elsewhere, but the operational behavior is not.

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

Conciseness3/5

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

Four words, so nothing is wasted, but it is a bare fragment rather than a front-loaded sentence, and its brevity comes at the cost of substance. It is short without being informative.

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?

For a lookup tool with a required argument and no annotations, the definition leaves critical gaps: parameter format, connection requirements, and error behavior. The existence of an output schema removes the need to describe return values, but everything else an agent needs to invoke this correctly is missing.

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?

The single required parameter class_name has 0% schema description coverage, and the description never mentions it — no format, no case sensitivity, no example such as 'Part' or 'Humanoid', no statement about what happens for unknown classes. The description does nothing to compensate for the schema gap.

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 says the tool returns 'class info' covering 'properties and events', which gives some substance beyond the name, but it never states a verb (fetch/describe) and never distinguishes it from siblings such as roblox_attrs, roblox_docs, or roblox_search, which plausibly surface similar metadata. Purpose is inferable but not crisp.

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?

There is no when-to-use guidance, no mention of prerequisites such as an active Studio connection or a loaded place, and no routing to alternatives. The agent must guess whether this or roblox_attrs/roblox_docs is the right call.

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