Skip to main content
Glama

Jabbertoon cartoon studio

by com.jabbertoon
OverviewDiscussionsAdmin

Build a thing in the 3D builder from steps, and link it

build
Read-only

Builds anything (a character, an animal, a car, a house) in Jabbertoon's 3D builder from steps, as its buttons do: spine, grow, bone (a skeleton, a bone at a time), add a ready part (leg, arm, head, wing, wheel, hat ...), set, copy, remove, look. Checks every step, says what was made (its parts and size) and gives a jabbertoon.com/editor/ link that opens it in the Forge, to change and use in a cartoon, world or game. Over MCP the answer also shows a picture of it from four sides. Steps that start {"op": "new", "kind": "move"} make a move from keys, {"op": "new", "kind": "world"} a world (a level is played to check it), and a game, every one in 3D: "walk" a place to walk at real size (played on foot: told what cannot be reached), or "trench", "space", "surface" or "sky" a game to fly. A refused step says where, why and how to fix it. export_link opens Export, free: STL/3MF to 3D print, glTF (Blender, Unity, Godot), SVG, Minecraft .schem. The steps: get_guide {"topic": "build"}, a game's {"topic": "game"}.

Input Schema

NameRequiredDescriptionDefault
buildNoA build to change (the build an answer gave); without it the steps start from a new spine.
stepsNoThe steps, in order: {op: spine | grow | bone | add | set | copy | remove | look, on (a part, or a name an earlier step gave with as), ...}.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / steps / description
      Previous value: -"The steps, in order: {op: spine | grow | add | set | copy | remove | look, on (a part, or a name an earlier step gave with as), ...}."New value: +"The steps, in order: {op: spine | grow | bone | add | set | copy | remove | look, on (a part, or a name an earlier step gave with as), ...}."
  2. Changed1 schema field changed
    • removedInput schema / properties / steps / items
      Removed value: -{
-  "type": "object"
-}
  3. Added

TDQS

B3/5.0
Behavior1/5

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

The description says the tool 'Builds anything', makes moves/worlds/games, opens Export, and produces editable links, all of which imply mutation and side effects. The annotations declare readOnlyHint=true, which directly contradicts the described write behavior and export functionality.

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 opening sentence is front-loaded with the core purpose, but the description is a dense run-on with many parentheticals and asides. It contains useful details, yet it is difficult to scan and some phrases, such as 'a game's {"topic": "game"}', are awkwardly structured.

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

Completeness4/5

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

For a complex nested-step tool with no output schema, the description covers a lot: step validation, returned link, four-side picture over MCP, export formats, and guide topics. Its main completeness gap is that the mutation semantics are described without reconciling them to the read-only annotation.

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 coverage is 100%, so the schema already documents both `build` and `steps`. The description adds some useful step-form examples, such as {"op": "new", "kind": "move"} and {"op": "new", "kind": "world"}, but much of its parameter discussion is embedded in long prose rather than clearly mapped to the two parameters.

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?

The description clearly states a specific verb and resource: building a 3D object in Jabbertoon's builder from ordered steps, including moves, worlds, and games. It lists the supported operations (spine, grow, bone, add, set, copy, remove, look) and names get_guide as a related tool, though it does not sharply differentiate itself from sibling tools such as validate.

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?

It gives some contextual guidance: use get_guide {"topic": "build"} for steps and {"topic": "game"} for games, and describes specific step kinds for moves, worlds, and games. However, it does not explicitly say when to use build versus validate or other siblings, nor does it state clear exclusions.

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

All Jabbertoon cartoon studio 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