HyperCodeMotion MCP

HyperCodeMotion Capabilities

get_capabilities

Read-onlyIdempotent

List the HyperCodeMotion JSON formats, layer types and properties, and effect presets that HyperCodeMotion Studio supports, how to reference files the user keeps in Studio by id, the screen rule that decides type size (field screen: the canvas wins over a requested size), a runtime layer that keeps an existing Lottie, glTF or GSAP file and seeks it, scene transitions (field transitions), a short start guide (field start), the names code layers and components must not redeclare (field reservedCodeNames), and the Studio contract revision they come from. Call it before designing.

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`start`	No
`screen`	Yes
`source`	No
`formats`	Yes
`presetSlots`	Yes
`transitions`	No
`userMaterials`	No
`fullyValidated`	Yes
`contractVersion`	Yes
`layerProperties`	Yes
`sourceSchemaSha`	No
`commonProperties`	No
`sourcePresetsSha`	No
`reservedCodeNames`	No
`layerPropertiesNote`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 27, 2026

addedOutput schema / properties / reservedCodeNames

Added value: +{
+  "properties": {
+    "codeLayer": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "component": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "rule": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

Changed4 schema fields changedOct 24, 2026
- addedOutput schema / properties / commonProperties
```
Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
```
- addedOutput schema / properties / layerPropertiesNote
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / properties / start
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / properties / transitions
```
Added value: +{
+  "type": "object"
+}
```

Changed2 schema fields changedOct 21, 2026

addedOutput schema / properties / screen
```
Added value: +{
+  "type": "string"
+}
```

changedOutput schema / required

Previous value: -[
-  "contractVersion",
-  "formats",
-  "layerProperties",
-  "presetSlots",
-  "fullyValidated"
-]New value: +[
+  "contractVersion",
+  "formats",
+  "layerProperties",
+  "presetSlots",
+  "screen",
+  "fullyValidated"
+]

Changed1 schema field changedOct 20, 2026
- addedOutput schema / properties / userMaterials
```
Added value: +{
+  "type": "string"
+}
```
First observedOct 14, 2026

TDQS

A3.7/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered. The description adds useful content context such as the contract revision and specific rules/fields, but does not disclose additional behavioral traits like caching, version compatibility handling, or auth requirements beyond what the annotations provide.

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 description is front-loaded with 'List the HyperCodeMotion...', which is good, but it continues as a single long run-on sentence with many comma-separated clauses. Every listed item is relevant, but the structure could be significantly clearer with bullets or shorter sentences.

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?

Given zero parameters, a rich annotation set, and an existing output schema, the description is largely complete: it states what the tool returns and when to call it. It could be improved by briefly clarifying that this is a static reference endpoint, but no critical information needed to invoke it correctly 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?

The tool takes zero parameters, so there are no parameter semantics to explain; the baseline for zero-parameter tools is 4. The description's references to fields like screen, transitions, start, and reservedCodeNames describe returned content, not input arguments, and do not create ambiguity.

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 tool lists HyperCodeMotion capabilities, including formats, layer types, presets, reference conventions, screen rules, runtime layers, transitions, start guide, reserved names, and contract revision. The specific verb 'List' and detailed content make the purpose unambiguous, but it does not explicitly distinguish itself from sibling tools such as get_template or get_motion_recipe.

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

Usage Guidelines4/5

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

The closing instruction 'Call it before designing' gives clear timing and context for using the tool. It does not name alternatives or state when not to use it, but for a prerequisite capabilities-reference endpoint this is adequate guidance.

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

All HyperCodeMotion MCP tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.