Skip to main content
Glama

Jabbertoon cartoon studio

by com.jabbertoon
OverviewDiscussionsAdmin

Read Jabbertoon's guide for writing a cartoon

get_guide
Read-only

Call this first. Returns one topic of Jabbertoon's guide as Markdown (under 20,000 characters): start (what it makes and the order of calls), cartoon (the JSON program: cast, scenes, lines, moves), text (the same cartoon as screenplay text), moves, characters, voices, places, errors, limits, build (the 3D builder's steps), export (a build as STL or 3MF to print, glTF, SVG blueprints, Minecraft), world (a world of blocks), walk (a place to walk), game (a game's steps), song (the editor's own file: characters, lines, moves, shots, a song), market, controls (pills, actions). Units everywhere: x and y are shares of the stage (0 to 1, the ground at 0.92), times are seconds. Example: {"topic": "cartoon"}.

Input Schema

NameRequiredDescriptionDefault
topicNoLeave it out for start, which names the others.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / topic / enum
      Previous value: -[
-  "start",
-  "cartoon",
-  "text",
-  "moves",
-  "characters",
-  "looks",
-  "voices",
-  "places",
-  "errors",
-  "limits",
-  "build",
-  "game",
-  "song",
-  "walk",
-  "play",
-  "export",
-  "shapes",
-  "examples",
-  "keys",
-  "world",
-  "market",
-  "controls",
-  "fight"
-]New value: +[
+  "start",
+  "cartoon",
+  "text",
+  "moves",
+  "characters",
+  "voices",
+  "places",
+  "errors",
+  "limits",
+  "build",
+  "game",
+  "song",
+  "walk",
+  "play",
+  "export",
+  "shapes",
+  "examples",
+  "keys",
+  "world",
+  "market",
+  "controls",
+  "fight"
+]
  2. Changed1 schema field changed
    • changedInput schema / properties / topic / enum
      Previous value: -[
-  "start",
-  "cartoon",
-  "text",
-  "moves",
-  "characters",
-  "looks",
-  "voices",
-  "places",
-  "errors",
-  "limits",
-  "build",
-  "game",
-  "song",
-  "walk",
-  "export",
-  "shapes",
-  "examples",
-  "keys",
-  "world",
-  "market",
-  "controls"
-]New value: +[
+  "start",
+  "cartoon",
+  "text",
+  "moves",
+  "characters",
+  "looks",
+  "voices",
+  "places",
+  "errors",
+  "limits",
+  "build",
+  "game",
+  "song",
+  "walk",
+  "play",
+  "export",
+  "shapes",
+  "examples",
+  "keys",
+  "world",
+  "market",
+  "controls",
+  "fight"
+]
  3. Changed1 schema field changed
    • changedInput schema / properties / topic / enum
      Previous value: -[
-  "start",
-  "cartoon",
-  "text",
-  "moves",
-  "characters",
-  "looks",
-  "voices",
-  "places",
-  "errors",
-  "limits",
-  "build",
-  "game",
-  "song",
-  "walk",
-  "export",
-  "shapes",
-  "examples",
-  "keys",
-  "world",
-  "market"
-]New value: +[
+  "start",
+  "cartoon",
+  "text",
+  "moves",
+  "characters",
+  "looks",
+  "voices",
+  "places",
+  "errors",
+  "limits",
+  "build",
+  "game",
+  "song",
+  "walk",
+  "export",
+  "shapes",
+  "examples",
+  "keys",
+  "world",
+  "market",
+  "controls"
+]
  4. Changed1 schema field changed
    • changedInput schema / properties / topic / enum
      Previous value: -[
-  "start",
-  "cartoon",
-  "text",
-  "moves",
-  "characters",
-  "looks",
-  "voices",
-  "places",
-  "errors",
-  "limits",
-  "build",
-  "game",
-  "song",
-  "walk",
-  "export",
-  "shapes",
-  "examples",
-  "keys",
-  "world"
-]New value: +[
+  "start",
+  "cartoon",
+  "text",
+  "moves",
+  "characters",
+  "looks",
+  "voices",
+  "places",
+  "errors",
+  "limits",
+  "build",
+  "game",
+  "song",
+  "walk",
+  "export",
+  "shapes",
+  "examples",
+  "keys",
+  "world",
+  "market"
+]
  5. Changed1 schema field changed
    • changedInput schema / properties / topic / enum
      Previous value: -[
-  "start",
-  "cartoon",
-  "text",
-  "moves",
-  "characters",
-  "looks",
-  "voices",
-  "places",
-  "errors",
-  "limits",
-  "build",
-  "game",
-  "song"
-]New value: +[
+  "start",
+  "cartoon",
+  "text",
+  "moves",
+  "characters",
+  "looks",
+  "voices",
+  "places",
+  "errors",
+  "limits",
+  "build",
+  "game",
+  "song",
+  "walk",
+  "export",
+  "shapes",
+  "examples",
+  "keys",
+  "world"
+]
  6. Changed1 schema field changed
    • changedInput schema / properties / topic / enum
      Previous value: -[
-  "start",
-  "cartoon",
-  "text",
-  "moves",
-  "characters",
-  "looks",
-  "voices",
-  "places",
-  "errors",
-  "limits",
-  "build",
-  "game"
-]New value: +[
+  "start",
+  "cartoon",
+  "text",
+  "moves",
+  "characters",
+  "looks",
+  "voices",
+  "places",
+  "errors",
+  "limits",
+  "build",
+  "game",
+  "song"
+]
  7. Changed1 schema field changed
    • changedInput schema / properties / topic / enum
      Previous value: -[
-  "start",
-  "cartoon",
-  "text",
-  "moves",
-  "characters",
-  "looks",
-  "voices",
-  "places",
-  "errors",
-  "limits",
-  "build"
-]New value: +[
+  "start",
+  "cartoon",
+  "text",
+  "moves",
+  "characters",
+  "looks",
+  "voices",
+  "places",
+  "errors",
+  "limits",
+  "build",
+  "game"
+]
  8. Changed1 schema field changed
    • changedInput schema / properties / topic / enum
      Previous value: -[
-  "start",
-  "cartoon",
-  "text",
-  "moves",
-  "characters",
-  "looks",
-  "voices",
-  "places",
-  "errors",
-  "limits"
-]New value: +[
+  "start",
+  "cartoon",
+  "text",
+  "moves",
+  "characters",
+  "looks",
+  "voices",
+  "places",
+  "errors",
+  "limits",
+  "build"
+]
  9. Added

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already cover read-only and closed-world, but the description adds genuinely new behavioral facts: output is Markdown capped under 20,000 characters, omission of topic defaults to 'start', and coordinate/time unit conventions (x,y as 0-1 shares of stage, ground at 0.92, seconds). It loses a point because the topic list in prose omits several enum values (play, shapes, examples, keys, fight), leaving a mild inconsistency an agent must resolve from the schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the imperative 'Call this first' and the return format, then the topic glossary, then units and an example. Dense but nearly every clause carries information; the topic parentheticals are the bulk and are justified by helping selection.

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?

No output schema exists, so the description must characterize the return value — it does so with format and size bound, plus unit conventions for the content it describes. Adequate for a one-parameter documentation tool, with only the topic-coverage mismatch against the enum as a gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the enum names the values, but the description goes further by glossing what each topic contains (cartoon = JSON program, export = STL/3MF/glTF/SVG/Minecraft, song = editor's own file), which genuinely aids topic selection. The gloss list does not match the enum exactly, so completeness of the explanation is imperfect.

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?

States a specific verb and resource ('Returns one topic of Jabbertoon's guide as Markdown') and enumerates the topics, so an agent knows this is the documentation tool rather than an action like build or validate. The 'Call this first' opener also frames its role in the toolset.

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

Usage Guidelines5/5

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

Explicitly says to call it first, and the schema note plus the 'start' topic description ('names the others') tells the agent how to bootstrap. No alternative needs mentioning because no sibling serves the same purpose.

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