Skip to main content
Glama

generate_frisbee

Generate a printable flying-disc frisbee with optional top decoration, then open an interactive 3D stage to orbit, zoom, and inspect the result.

Instructions

Generate a flying-disc frisbee with optional top decoration. Opens Kiln's interactive inline 3D stage on the result (orbit/zoom panel in MCP Apps hosts; hosted sessions add a browser stage link). MAKE DOORS: design_session, Kiln's front door for making an object, is not installed here (signed in to Kiln it runs on Kiln's servers). On this install compile_scad IS the make → preview → iterate loop: make it, show the preview, iterate.

INLINE 3D STAGE: on success this tool opens Kiln's interactive 3D stage — an inline viewer panel the user can orbit, zoom, and turn over — in hosts that render MCP Apps panels (Kiln's hosted connection attaches a browser stage link for hosts that don't). Oversized meshes are decimated automatically for the stage; the PNG preview is the floor, not the whole experience.

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": "generate_frisbee"
  }
}

Input Schema

NameRequiredDescriptionDefault
size_mmNoDisc diameter in mm (default 230 — regulation). Default: 230.0.
brief_idNoOptional saved-goal id from ``design_session``. When supplied, the produced mesh gets a ``design_brief:<id>`` intent sidecar so the audit's "matches what you asked for" gate, the brief failure_history wiring, and the ``compare_design_versions`` intent diff all light up against the saved goal. Omit to skip — REST callers without a goal still get an auto-inferred brief at dispatch time. Default: "".
materialNoMaterial (default PLA). Default: "PLA".
body_colorNoBody color (default white). Default: "white".
decorationNoTop surface content — ``"text:..."`` for debossed text, a PNG/JPG path for an embossed image, or empty for plain. Default: "".
photo_maskNoPhoto crop shape for a photograph (a logo on a clean field is carved unmasked whatever is passed; a name outside this list is refused) — ``"circle"`` (the default; empty or ``"auto"`` reads the same, since the disc is round), ``"rectangle"`` or ``"rounded_rectangle"``. Default: "circle".
include_stepNoAlso emit a CAD-exact STEP file — REAL analytic B-rep (true cone taper, exact spheroid dome as an analytic surface of revolution), never a tessellated conversion. On success the response gains a ``step`` block with ``step_path``. Text and image decoration refuse honestly (the flight plate is a domed surface) — the mesh outputs are always unaffected. Default: false.
lip_width_mmNoOuter lip width in mm (default 8). Default: 8.0.
thickness_mmNoBase plate thickness in mm (default 3). Default: 3.0.
lip_height_mmNoOuter lip height in mm (default 12). Default: 12.0.
color_overridesNoJSON dict mapping role → color name/hex. Default: "".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed11 schema fields changedv1.5.1
    • changedInput schema / properties / body_color / description
      Previous value: -"Default: \"white\"."New value: +"Body color (default white). Default: \"white\"."
    • changedInput schema / properties / brief_id / description
      Previous value: -"Default: \"\"."New value: +"Optional saved-goal id from ``design_session``. When supplied, the produced mesh gets a ``design_brief:<id>`` intent sidecar so the audit's \"matches what you asked for\" gate, the brief failure_history wiring, and the ``compare_design_versions`` intent diff all light up against the saved goal.  Omit to skip — REST callers without a goal still get an auto-inferred brief at dispatch time. Default: \"\"."
    • changedInput schema / properties / color_overrides / description
      Previous value: -"Default: \"\"."New value: +"JSON dict mapping role → color name/hex. Default: \"\"."
    • changedInput schema / properties / decoration / description
      Previous value: -"Default: \"\"."New value: +"Top surface content — ``\"text:...\"`` for debossed text, a PNG/JPG path for an embossed image, or empty for plain. Default: \"\"."
    • changedInput schema / properties / include_step / description
      Previous value: -"Default: false."New value: +"Also emit a CAD-exact STEP file — REAL analytic B-rep (true cone taper, exact spheroid dome as an analytic surface of revolution), never a tessellated conversion.  On success the response gains a ``step`` block with ``step_path``.  Text and image decoration refuse honestly (the flight plate is a domed surface) — the mesh outputs are always unaffected. Default: false."
    • changedInput schema / properties / lip_height_mm / description
      Previous value: -"Default: 12.0."New value: +"Outer lip height in mm (default 12). Default: 12.0."
    • changedInput schema / properties / lip_width_mm / description
      Previous value: -"Default: 8.0."New value: +"Outer lip width in mm (default 8). Default: 8.0."
    • changedInput schema / properties / material / description
      Previous value: -"Default: \"PLA\"."New value: +"Material (default PLA). Default: \"PLA\"."
    • changedInput schema / properties / photo_mask / description
      Previous value: -"Default: \"circle\"."New value: +"Photo crop shape for a photograph (a logo on a clean field is carved unmasked whatever is passed; a name outside this list is refused) — ``\"circle\"`` (the default; empty or ``\"auto\"`` reads the same, since the disc is round), ``\"rectangle\"`` or ``\"rounded_rectangle\"``. Default: \"circle\"."
    • changedInput schema / properties / size_mm / description
      Previous value: -"Default: 230.0."New value: +"Disc diameter in mm (default 230 — regulation). Default: 230.0."
    • changedInput schema / properties / thickness_mm / description
      Previous value: -"Default: 3.0."New value: +"Base plate thickness in mm (default 3). Default: 3.0."
  2. Addedv1.5.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations only cover the safety profile (readOnlyHint false, destructiveHint false, openWorldHint false). The description adds real behavioral context: the interactive inline 3D stage is opened on the result, hosted sessions attach a browser stage link, oversized meshes are decimated automatically, and the PNG preview is a floor rather than the full experience. That is meaningful disclosure beyond the annotations.

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?

The purpose is front-loaded in the first clause, but the body is padded with editorial meta-commentary about which tools are installed on this host and rhetorical phrasing like 'the PNG preview is the floor, not the whole experience.' The stage behavior is worth stating; the installation commentary largely is not.

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

Completeness3/5

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

For an 11-parameter generative tool with no output schema, the description covers the stage/preview behavior well, but it says nothing about generation time, what the textual result contains, or how decoration and material choices affect output. Adequate but not complete.

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 the 11 parameters including size_mm, decoration, photo_mask, and include_step are already fully documented. The description only gestures at 'optional top decoration' and adds no syntax or interaction details for parameters the schema does not already cover. Baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The opening sentence gives a specific verb and resource ('Generate a flying-disc frisbee') plus its main optional feature ('optional top decoration'), which separates it cleanly from the many other shape-generator siblings such as generate_coaster or generate_pet_bowl.

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

Usage Guidelines3/5

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

The 'MAKE DOORS' paragraph tries to place the tool in a workflow, but it mostly talks about design_session and compile_scad rather than when to pick generate_frisbee over a sibling generator. The agent can infer it is for frisbee-shaped objects, but there is no explicit when/when-not guidance or named alternative generator.

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

Deploy Server

Other Tools