Skip to main content
Glama

Generate Motion Tokens

generate_motion_tokens

Generates duration and easing tokens for instant-to-slow motion with standard, enter, exit and spring curves in snappy, balanced or relaxed styles, plus prefers-reduced-motion overrides.

Instructions

Duration and easing tokens (instant to slower; standard, enter, exit, spring) in a snappy, balanced or relaxed feel, with an automatic prefers-reduced-motion override. Deterministic, no API key needed.

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

Input Schema

NameRequiredDescriptionDefault
styleNobalanced

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does add real behavior: an automatic prefers-reduced-motion override, determinism, and no API key requirement. It omits the output format (CSS custom properties vs. JSON token object) and how the reduced-motion variant is surfaced, which matters for a generation tool.

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?

Two dense sentences, front-loading the token scope before the accessibility and determinism notes; nothing is filler. The phrasing 'in a snappy, balanced or relaxed feel' is slightly compressed but readable.

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 simple one-optional-param generator with no output schema, the description covers what is produced and one key behavioral guarantee. It stops short of describing the return shape, which is the main thing an agent needs before wiring the output into a stylesheet.

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 0% and the single parameter is an enum, so the schema only lists snappy/balanced/relaxed without meaning. The description repeats those three values but never explains what each feel does to duration or easing curves, so it adds little over the schema.

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 names a specific resource (duration and easing tokens) and enumerates the concrete categories produced (standard, enter, exit, spring; instant to slower), which is far more than a restatement of the name. It does not, however, distinguish this from the many other generate_* token tools in the sibling set.

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

Usage Guidelines2/5

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

There is no explicit when-to-use statement, no when-not-to-use condition, and no named alternative. The agent can infer that it is for motion tokens, but nothing tells it whether to reach for this versus generate_type_scale or generate_shadows when building a larger system.

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