Skip to main content
Glama

Ready-made easing

get_easing
Read-only

Returns named easing curves as CSS cubic-bezier or linear(), Motion values, and GSAP names, and computes spring parameters into linear() with duration.

Instructions

Returns an easings.net curve as CSS (cubic-bezier or linear()), values for Motion, and the matching GSAP name. With spring, computes a spring (stiffness, damping, mass) and returns linear() plus its duration.

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

Input Schema

NameRequiredDescriptionDefault
nameNoE.g. easeOutCubic, easeInOutBack, easeOutBounce
springNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare a read-only, closed-world operation; the description adds useful output behavior by naming the CSS, Motion, GSAP, and spring return formats. It still omits error/fallback behavior and parameter-combination rules, so it is good but not fully transparent.

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?

Two compact sentences are front-loaded with the main output modes and contain no filler; the spring mode is explained in the second sentence. The wording is efficient for the amount of behavior covered.

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

Completeness3/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 does a good job naming return formats, and annotations cover safety. However, with two optional params and a nested spring object, it does not specify the no-argument case or precedence when both `name` and `spring` are provided, leaving invocation ambiguity.

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 coverage is 50%, and the description adds meaning for `spring` by naming stiffness, damping, and mass and describing its returned linear() duration. It leaves `name` implicit and does not explain defaults, optionality, or interaction between `name` and `spring`, so it only partly compensates for the schema gap.

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 gives a specific verb ('Returns') and identifies the exact resources: an easings.net curve as CSS, Motion values, GSAP name, or a computed spring with linear() and duration. This is specific enough to distinguish it from the unrelated sibling tools, which deal with components, icons, gradients, and palettes.

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?

It indicates that supplying `spring` switches to computed spring output, but it does not state when to choose named curves versus spring, when not to use either, or what happens if both or neither are supplied. Usage is therefore implied rather than explicitly guided.

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