Skip to main content
Glama

Eased gradient

easing_gradient
Read-only

Generates CSS linear-gradients with color stops spaced along an easing curve to avoid hard edges, useful for image scrims and section transitions.

Instructions

Generates a CSS linear-gradient with stops spaced along an easing curve, without the hard edge of linear gradients. Good for scrims over images and transitions between sections.

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": {
      "from": "<from>"
    },
    "name": "easing_gradient"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNotransparent
fromYesStart color, e.g. #000 or rgb(0 0 0 / .8)
stepsNo
easingNoeaseInOutSine
directionNoE.g. to bottom, 45degto bottom

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 readOnlyHint=true and openWorldHint=false, so safety is covered; the description earns credit by explaining the actual behavior — stop spacing follows an easing curve rather than being uniform, which is the substantive thing an agent can't infer. It stops short of describing the return form (bare function vs. full declaration) or how steps count affects output.

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 sentences, front-loaded with what it produces, followed by when it's useful. No filler, no restating of the title.

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?

For a pure generator with no output schema and five parameters, the description never states what is actually returned (a `linear-gradient(...)` value? a full CSS declaration?) or how step count trades off quality versus size. Adequate to select the tool, thin on invoking it correctly.

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 40%, so the description has to do some work: 'stops spaced along an easing curve' indirectly explains steps and easing, which is genuine added meaning. However, from/to colors, the 'to bottom' direction format, and the transparent default are left entirely to the schema, so compensation is only partial.

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?

Specific verb plus specific artifact: 'Generates a CSS linear-gradient with stops spaced along an easing curve.' The resource is described precisely enough to separate it from get_easing (curve data) and make_palette (color sets), but no sibling is named and the relationship to get_easing — whether the easing names here mirror that tool — is left implicit.

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 concrete use contexts ('scrims over images', 'transitions between sections') and states the differentiator versus ordinary linear gradients ('without the hard edge'). It does not say when not to use it or what to use for hard-edged/stepped gradients, so the routing is clear but not complete.

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