Skip to main content
Glama

studmill

by com.studmill
OverviewDiscussionsAdmin

generate_variants

Generate 2–4 variants of one Roblox prop prompt. Returns one generation_id immediately; poll get_generation until every requested variant is complete. Each variant runs the full pipeline and counts individually against quota.

Input Schema

NameRequiredDescriptionDefault
styleNoStyle preset. Default low-poly.
promptYesWhat to generate.
variantsYesNumber of variants (2–4).
size_studsNoOptional real-world size: the longest side of the finished model in studs (1 stud = 0.28 m), e.g. 6 for a park bench, 25 for a small house. Omit to use the model's default size.
tri_budgetNoTriangle budget per variant (500–10000). Default 10000. Models are decimated to it, then measured.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / size_studs
      Added value: +{
+  "description": "Optional real-world size: the longest side of the finished model in studs (1 stud = 0.28 m), e.g. 6 for a park bench, 25 for a small house. Omit to use the model's default size.",
+  "maximum": 2048,
+  "minimum": 0.5,
+  "type": "number"
+}
    • changedInput schema / properties / tri_budget / description
      Previous value: -"Triangle target per variant (500–10000). Default 10000."New value: +"Triangle budget per variant (500–10000). Default 10000. Models are decimated to it, then measured."
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full burden and does so well: it discloses the async contract (returns one generation_id immediately), the required polling loop, per-variant pipeline execution, and individual quota consumption. It omits error/timeout behavior and any auth or latency expectations, keeping it short of a 5.

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?

Three sentences, each earning its place: purpose, async return plus polling instruction, and cost caveat. Front-loaded with what the tool does before the operational details.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For an async tool with no output schema, the description covers the essential call contract: what is returned immediately, how to retrieve results, and the quota implication. Nothing an agent needs to invoke and then follow up correctly is missing.

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 parameters are already documented (size_studs example values, tri_budget decimation note, style default). The description adds only the 2–4 variant range, which is redundant with the schema's minimum/maximum. Baseline 3 applies.

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 with precise scope: 'Generate 2–4 variants of one Roblox prop prompt.' The variant-count scope implicitly separates it from the single-asset sibling generate_asset, though it never names that sibling explicitly the way a top-tier definition would.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives clear follow-up workflow: poll get_generation until every variant completes, and warns each variant is billed individually against quota. It does not state when to prefer generate_asset over this tool, so the alternative-selection guidance is only implicit.

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

All studmill toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources