Skip to main content
Glama

studio_export_model

Save a managed build root as a private local binary Roblox model under generated/exports.

Instructions

Save a managed build root as a private local binary Roblox model under generated/exports.

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

Input Schema

NameRequiredDescriptionDefault
rootPathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.2.3

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses the output location (generated/exports), that the artifact is a binary Roblox model, and that it is private and local, but says nothing about overwrite behavior, permissions required, or what is returned on success.

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?

One sentence that front-loads the action and packs destination, format, and visibility into minimal text with no filler.

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 mutation tool with no annotations and no output schema, the description omits return behavior and side effects such as overwriting an existing file at the destination. It is adequate to identify the tool but not fully sufficient to call it correctly.

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 0% for the single rootPath parameter, so the description must compensate. It adds some meaning by indicating the path must refer to a managed build root, but gives no format, relative-vs-absolute, or validation guidance.

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?

States a specific verb and resource: saves a managed build root as a Roblox model and names the destination directory generated/exports. No sibling tool performs exports, so it is distinguishable, though the phrase 'managed build root' assumes prior context about what that means.

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 explicit when-to-use or when-not-to-use guidance and no mention of alternatives. The only usage signal is implied by 'managed build root', which narrows the input scope but doesn't tell an agent when exporting is the right move versus e.g. studio_read_output.

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