Skip to main content
Glama
Sign In

Designers

by com.allthepossibles
OverviewDiscussionsAdmin

Easing designer

design_easing
Read-only

Describe an easing and get CSS back. Pass easing as a name (ease, ease-out, ease-out-cubic, ease-in-out-quart, ease-out-back and others), as cubic-bezier(x1,y1,x2,y2) (x values must sit between 0 and 1), or as spring with optional mass, stiffness, damping. Optional duration_ms (bezier only; a spring has its own settle time). Returns the CSS timing function, a CSS linear() version, 11 sampled points of progress against time, overshoot and settle figures for springs, and notes on feel with a convention for when to use it. The named curve values are widely shared conventions, not a standard beyond the five CSS keywords.

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": {
      "easing": "<easing>"
    },
    "name": "design_easing"
  }
}

Input Schema

NameRequiredDescriptionDefault
massNoSpring mass, default 1
easingYesName, cubic-bezier(x1,y1,x2,y2) or spring
dampingNoSpring damping, default 26
stiffnessNoSpring stiffness, default 170
duration_msNoDuration in ms (bezier only), 1 to 10000

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior5/5

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

Annotations already establish a safe read-only, non-destructive, closed-world operation. The description adds substantial behavioral context beyond that: accepted easing forms, cubic-bezier x-value constraints, duration applicability only to bezier, spring settle behavior, and exactly what the response includes.

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 action and result, followed by input forms and return details. Every sentence carries useful information, and there is no filler.

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?

There is no output schema, so the description carries the burden of explaining returns, which it does thoroughly: CSS timing function, linear() form, sampled progress points, overshoot/settle figures, and feel notes. Combined with annotations covering safety, the definition is complete enough for an agent to invoke it correctly.

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 a baseline of 3 is appropriate. The description still adds value by illustrating named curves, spelling out cubic-bezier syntax constraints, and clarifying that duration_ms applies only to bezier while mass, stiffness, and damping are spring options.

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 gives a specific verb and resource: describe an easing and return CSS. It clearly frames the tool as an easing-to-CSS generator, though it does not explicitly distinguish itself from motion-related siblings such as check_motion, audit_motion_css, or plan_durations.

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 by the input formats and return description, but the text never says when to choose this tool over motion-audit or duration-planning alternatives. It explains how to call the tool more than when to call it.

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

All Designers toolsInspect
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