Skip to main content
Glama
Sign In

Jabbertoon cartoon studio

by com.jabbertoon
OverviewDiscussionsAdmin

Get one move's program and readable text

get_move
Read-only

Returns one move or word. A Do list move (by id c4c:beh:wave_hello, short name or page slug): its block program as JSON and screenplay text, the motion language's lines that play it, its length, settings, page and links. A motion language word (people.sneak, or sneak): its form, dials, bodies and whole text. Example: {"move": "wave_hello"}.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "move": "<move>"
    },
    "name": "get_move"
  }
}

Input Schema

NameRequiredDescriptionDefault
moveYesIts id, short name or page slug, as list_moves gives them.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / move / description
      Previous value: -"The move's id (c4c:beh:wave_hello), short name (wave_hello) or page slug, as list_moves gives them."New value: +"Its id, short name or page slug, as list_moves gives them."
    • 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": {
-    "content_hash": {
-      "type": "string"
-    },
-    "description": {
-      "type": "string"
-    },
-    "error": {
-      "$ref": "#/$defs/problem"
-    },
-    "id": {
-      "type": "string"
-    },
-    "license": {
-      "type": "string"
-    },
-    "links": {
-      "type": "object"
-    },
-    "name": {
-      "type": "string"
-    },
-    "notes": {
-      "items": {
-        "type": "string"
-      },
-      "type": "array"
-    },
-    "ok": {
-      "type": "boolean"
-    },
-    "pack_slug": {
-      "type": "string"
-    },
-    "program": {
-      "description": "The move's block program (JSON).",
-      "type": "object"
-    },
-    "seconds": {
-      "type": [
-        "number",
-        "null"
-      ]
-    },
-    "skeleton": {
-      "type": "boolean"
-    },
-    "slug": {
-      "type": "string"
-    },
-    "text": {
-      "description": "The same program as readable text, one block per line.",
-      "type": "string"
-    },
-    "url": {
-      "description": "The move's page on jabbertoon.com (the list of moves when the move is not found).",
-      "type": "string"
-    },
-    "version": {
-      "type": "string"
-    }
-  },
-  "required": [
-    "ok",
-    "url"
-  ],
-  "type": "object"
-}New value: +null
  2. First observed

TDQS

A4.5/5.0
Behavior5/5

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

With only readOnlyHint and openWorldHint annotations, the description carries the burden of describing what the tool returns. It does so in detail for both move types, including block program JSON, screenplay text, motion language lines, length, settings, page, links, and word attributes such as form and dials. This is substantially useful behavioral context 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.

Conciseness5/5

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

The description is front-loaded with the core purpose, then splits into the two supported cases, and ends with a compact example. There is no filler; every clause conveys relevant scope or return details.

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

Completeness5/5

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

For a one-parameter read-only getter with no output schema, the description supplies enough detail about accepted inputs and returned data for an agent to call it correctly. It covers both supported entity types and the main response fields, so no critical context is missing.

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 baseline is 3. The description adds concrete identifier examples beyond the schema: 'c4c:beh:wave_hello' for a move, 'people.sneak' or 'sneak' for a word, plus an example invocation. It meaningfully clarifies accepted identifier forms.

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 description states a specific verb and resource: it returns exactly one move or word. It clearly distinguishes the two cases it handles: a Do list move with program JSON/screenplay text, and a motion language word with form/dials/bodies. This goes well beyond the title and makes the tool's 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?

Usage is implied: call this to retrieve a single move or word when you already have its identifier from list_moves. The schema notes that identifiers come from list_moves, but the description itself does not explicitly say when to use this instead of list_moves or other siblings. No exclusions or alternatives are stated.

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