Motion Menu

adapt_pattern

Adapt a pattern to a brand system. Pass a pattern slug/number and a brand (colors, typography, spacing, radius) and get back the pattern's HTML/CSS/JS with every visual token replaced by the brand's values. The pattern's behavior, motion, and structure are preserved — only its visual expression changes. This is how a client gets THEIR pattern, not a generic one. FREE, no key required.

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": {
      "slug": "<slug>",
      "brand": "<brand>"
    },
    "name": "adapt_pattern"
  }
}

Input Schema

Name	Required	Description	Default
`slug`	Yes	pattern slug or number to adapt
`brand`	Yes	the brand system to adapt to

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 6, 2026

TDQS

A4.1/5.0

Behavior4/5

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

No annotations exist, so the description carries the full burden and does substantial work: it discloses what is preserved (behavior, motion, structure) and what changes (visual expression only), plus the output shape and the free/no-key access condition. Gaps remain around failure behavior for an unknown slug and whether the call has any side effects.

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 purpose, then the transformation contract, then a differentiation sentence and an access note. Every sentence carries information, though the capitalized 'THEIR' and 'not a generic one' lean promotional rather than strictly functional.

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?

There is no output schema, and the description correctly compensates by naming the return artifacts (HTML/CSS/JS). For a two-parameter nested-object tool whose schema is fully described, the only meaningful omissions are error/edge-case behavior and how the resulting pattern is consumed downstream.

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

Parameters3/5

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

Schema description coverage is 100% and the nested brand object documents its own required sub-fields and enums, so the schema does the heavy lifting. The description only restates the brand facets (colors, typography, spacing, radius) without adding format details such as color string syntax or how slug values map to list_patterns output.

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+resource (adapt a pattern to a brand system) and spells out the transformation contract: pattern HTML/CSS/JS returned with every visual token replaced. The line 'This is how a client gets THEIR pattern, not a generic one' implicitly separates it from get_pattern, which returns the unadapted version.

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?

Gives a clear trigger condition: use when you have a brand system (colors, typography, spacing, radius) and want the pattern expressed in it. It also flags zero cost/'no key required', which is a real invocation signal. It stops short of naming an explicit alternative or a when-not-to-use case, so no exclusion guidance.

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

All Motion Menu 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.

Resources

Need Help?