Skip to main content
Glama
Sign In

Jabbertoon cartoon studio

by com.jabbertoon
OverviewDiscussionsAdmin

List the moves and words a character can do

list_moves
Read-only

Lists what a character can do: the Do list's moves (wave hello, hop, bow...), each with the motion language's lines that play it (a does block plays one by id), and the motion language's own words (swim_to, hover, on_guard, sneak...) with their dials. category: humanoid, mammal, bird, fish or fantasy. q: words to match, or what a word means (dance finds Groove). Example: {"q": "wave", "category": "humanoid"}.

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

Input Schema

NameRequiredDescriptionDefault
qNoWords to look for ("wave", "dance"); leave it out for every move.
categoryNoOne kind of body.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / category
      Added value: +{
+  "description": "One kind of body.",
+  "enum": [
+    "humanoid",
+    "mammal",
+    "bird",
+    "fish",
+    "fantasy"
+  ],
+  "type": "string"
+}
  2. Changed2 schema fields changed
    • changedInput schema / properties / q / description
      Previous value: -"Words to look for in a move's name, id or description, or what the move does, e.g. \"wave\", \"walk in\" or \"dance\". Leave it out to list every move."New value: +"Words to look for (\"wave\", \"dance\"); leave it out for every move."
    • 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": {
-    "count": {
-      "description": "How many moves are listed here.",
-      "type": "integer"
-    },
-    "error": {
-      "$ref": "#/$defs/problem"
-    },
-    "filters": {
-      "description": "The filters this answer used, exactly as given.",
-      "type": "object"
-    },
-    "moves": {
-      "items": {
-        "properties": {
-          "description": {
-            "type": "string"
-          },
-          "id": {
-            "description": "The pack id, e.g. c4c:beh:wave_hello.",
-            "type": "string"
-          },
-          "license": {
-            "type": "string"
-          },
-          "links": {
-            "description": "Links that open the move: blocks (the block editor) and studio (the cartoon studio).",
-            "type": "object"
-          },
-          "name": {
-            "type": "string"
-          },
-          "pack_slug": {
-            "description": "The short name used in #p= links, e.g. wave_hello.",
-            "type": "string"
-          },
-          "seconds": {
-            "description": "How long the move's preview plays, in seconds.",
-            "type": [
-              "number",
-              "null"
-            ]
-          },
-          "skeleton": {
-            "description": "True for the moves that bend chains, reach with hands or turn between views.",
-            "type": "boolean"
-          },
-          "slug": {
-            "description": "The last part of the move's page URL.",
-            "type": "string"
-          },
-          "url": {
-            "description": "The move's page on jabbertoon.com.",
-            "type": "string"
-          },
-          "version": {
-            "type": "string"
-          }
-        },
-        "required": [
-          "id",
-          "slug",
-          "name",
-          "url"
-        ],
-        "type": "object"
-      },
-      "type": "array"
-    },
-    "notes": {
-      "items": {
-        "type": "string"
-      },
-      "type": "array"
-    },
-    "ok": {
-      "type": "boolean"
-    },
-    "total": {
-      "description": "How many moves there are in all.",
-      "type": "integer"
-    },
-    "url": {
-      "description": "The page that lists every move.",
-      "type": "string"
-    }
-  },
-  "required": [
-    "ok",
-    "url"
-  ],
-  "type": "object"
-}New value: +null
  3. First observed

TDQS

A3.6/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 safety behavior is covered. The description adds useful output-content context by saying each move includes lines that play it and words include their dials, but it does not discuss pagination, ordering, or exact return shape.

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?

The description is front-loaded with the tool's scope and remains reasonably compact. It is dense and somewhat convoluted in the parenthetical about a does block playing a line by id, but the example at the end keeps it actionable.

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?

With full schema coverage, safety annotations, and only two optional parameters, the definition provides enough context to call the tool. It also describes the kinds of results returned, though exact response structure or ordering is not specified and no output schema exists.

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%, so the schema already documents q and category. The description adds a meaningful semantic nuance beyond the schema by explaining that q can match what a word means, illustrated by 'dance finds Groove', and provides a concrete combined-parameter example.

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 that this lists a character's moves, their motion-language lines, and motion-language words with dials. It does not explicitly differentiate from nearby tools such as get_move or list_characters, so it is clear but lacks sibling routing.

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?

An example query shows intended use with q and category, implying this is for discovering moves or words. However, it does not state when to use this versus get_move or other siblings, nor does it give 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