Skip to main content
Glama

Jabbertoon cartoon studio

by com.jabbertoon
OverviewDiscussionsAdmin

List Jabbertoon's ready-made cartoon characters and voices

list_characters
Read-only

Lists the cast in 3D: the six people (bob, ria, sunny, sam, lee, rose) and the animals (dog, cat, fox, horse, gull, and bear2, fox2, rabbit2, raccoon2, cat2 on two legs), each with the designed entry a cast entry gives it and a voice; the voices a line can use; and cartoon_example, a whole talking cartoon to copy. (The six flat templates of older cartoons are listed too, as characters.) Call it to write a cast: {"dog": {"name": "Biscuit", "look": {"template": "dog", "colors": {"skin": "#8d6e63"}}, "voice": "am_puck"}}.

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -{
-  "$defs": {
-    "problem": {
-      "properties": {
-        "code": {
-          "type": "string"
-        },
-        "fix": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "says": {
-          "type": "string"
-        },
-        "where": {
-          "type": [
-            "string",
-            "null"
-          ]
-        }
-      },
-      "required": [
-        "code",
-        "where",
-        "says",
-        "fix"
-      ],
-      "type": "object"
-    }
-  },
-  "properties": {
-    "cartoon_example": {
-      "description": "A whole talking cartoon file ({cast, program}) to copy: give it to validate as cartoon.",
-      "type": "object"
-    },
-    "cast_entry_example": {
-      "description": "One cast entry that draws the first character: the value under a cast id, as in {\"cast\": {\"A\": <this>}}.",
-      "type": "object"
-    },
-    "characters": {
-      "items": {
-        "properties": {
-          "colors": {
-            "description": "The look.colors keys (body, skin, acc), what each paints on this character, and the default colour.",
-            "type": "array"
-          },
-          "id": {
-            "description": "The character pack id (c4c:char:<slug>) when the pack is published, else null.",
-            "type": [
-              "string",
-              "null"
-            ]
-          },
-          "legs": {
-            "type": "integer"
-          },
-          "links": {
-            "description": "Links that open it: studio (put it in a cartoon) and create (start a new character from it).",
-            "type": "object"
-          },
-          "name": {
-            "type": "string"
-          },
-          "options": {
-            "description": "The look.options keys this character has, with their values.",
-            "type": "array"
-          },
-          "slug": {
-            "type": "string"
-          },
-          "template": {
-            "description": "What a cast entry's look.template says to draw this character.",
-            "type": "string"
-          },
-          "url": {
-            "description": "The character's page on jabbertoon.com.",
-            "type": "string"
-          },
-          "views": {
-            "description": "The views it is drawn in; the first is its own.",
-            "items": {
-              "type": "string"
-            },
-            "type": "array"
-          }
-        },
-        "required": [
-          "slug",
-          "name",
-          "template",
-          "url"
-        ],
-        "type": "object"
-      },
-      "type": "array"
-    },
-    "count": {
-      "type": "integer"
-    },
-    "error": {
-      "$ref": "#/$defs/problem"
-    },
-    "notes": {
-      "items": {
-        "type": "string"
-      },
-      "type": "array"
-    },
-    "ok": {
-      "type": "boolean"
-    },
-    "url": {
-      "description": "The page that lists every character.",
-      "type": "string"
-    }
-  },
-  "required": [
-    "ok",
-    "url"
-  ],
-  "type": "object"
-}New value: +null
  2. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds useful inventory context (which characters, which voices, cartoon_example) but is vague about the actual return shape ('the designed entry a cast entry gives it') and says nothing about freshness, limits, or how the cast relates to the write path.

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?

It is front-loaded with the core purpose, but the middle sentence is a long, grammatically tangled run-on that is hard to parse. Several phrases ('the designed entry a cast entry gives it') add words without adding clarity.

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?

With no output schema, the description must carry the return-value burden; it does list the main contents (cast, voices, cartoon_example, flat templates) but explains their structure opaquely. Enough to know roughly what comes back, not enough to know the shape.

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?

There are zero parameters, so the baseline is 4. The description even shows the object shape an agent would supply when writing a cast, which is helpful orientation even though it is not a parameter of this tool.

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 ('Lists the cast in 3D') and enumerates the actual members (bob, ria, sunny, sam, lee, rose; dog, cat, fox, etc.), so an agent can distinguish it from list_looks and list_moves. It does not explicitly name a sibling it replaces, but the character/voice inventory makes the scope unambiguous.

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?

'Call it to write a cast' plus a concrete JSON sample implies the usage context clearly, but there is no statement of when NOT to call it or which sibling to prefer for other listing needs (looks, moves). Adequate but leaves the alternatives to inference.

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