Skip to main content
Glama
Roblox Studio MCP Gateway

Roblox Studio MCP Gateway

by camilin7483

roblox_docs

Retrieve Roblox engine reference documentation by name and category to look up classes and APIs without opening Roblox Studio.

Instructions

Roblox engine reference docs (public, no Studio needed).

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": {
      "name": "<name>"
    },
    "name": "roblox_docs"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
categoryNoclasses

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.6/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose one meaningful behavioral trait: the docs are public and require no Studio connection, which tells the agent it can call this without a ready session. It says nothing about read-only semantics, rate limits, or lookup failure behavior for unknown names.

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?

It is a single short fragment with no wasted words, which is good front-loading. But brevity here comes at the cost of specification rather than from efficiency — the one clause present is mostly the parenthetical caveat.

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 needn't be described. However, with no annotations, 0% parameter coverage, and an unenumerated category parameter, a one-line description is not enough for an agent to call this correctly — the category semantics are the critical missing piece.

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%, so both parameters (name, category with default "classes") are undocumented anywhere. The description doesn't explain that name is the class/member identifier or what values category accepts — the default "classes" hints at alternatives that are never listed.

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?

"Roblox engine reference docs" names the resource but is a noun fragment with no verb — it doesn't say whether it retrieves, searches, or lists docs. "(public, no Studio needed)" does distinguish it from the Studio-bound siblings, which helps, but what a caller actually gets back is left to inference.

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 parenthetical implies the tool works without a live Studio session, which is a weak usage cue. There is no explicit when-to-use, no statement of what to do instead when a Studio session is available, and no mention of siblings like roblox_class or roblox_search that an agent might confuse with doc lookup.

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